> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/settings/profile.md). # Your profile Set your name, timezone and public booking details before sharing a link. Open your profile from **Settings**. ## Check your details Review your name, profile image, public name, booking handle, title and contact details where shown. Your booking handle is used in public booking URLs; changing it can affect links you have already shared. Choose the timezone you normally work in. Distro uses your working hours and calendar availability to offer times; your prospect can view the same meeting in their own timezone. Save your changes and preview a personal booking page. Check that the displayed name, image and meeting information are what you want a guest to see. ## Finish your setup Connect [Google Calendar](/integrations/google-calendar.md) or [Outlook Calendar](/integrations/outlook-calendar.md). Then set [Working hours](/settings/working-hours.md), choose conferencing and share a [Booking link](/scheduling/booking-links.md). A profile is not a CRM owner mapping. An admin maps your connected identities separately when workflows must assign records or send through another tool. If a setting is missing, confirm whether you are editing your own personal settings or workspace settings. Changing the workspace does not mean every teammate's profile or calendar is connected. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/settings/profile.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.