> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/integrations/chrome-extension/share-links.md). # Share links Click the Distro toolbar icon and open **Scheduling**. Find your personal, group, or reusable outbound link and use its copy action. Paste the link into your message when you're ready. Use the preview action to check what the recipient will see. Actions such as editing or creating the underlying link may open the Distro app. ## Keep frequently used links close Use a link's star control to save it as a favorite. Saved links appear together under **Preferred** in the side panel and command palette, and under **Favorites** in the `di/` picker. These are the same saved choices across the extension. Removing a favorite doesn't delete the link. ## More than copying Open the link's actions to [offer times](/integrations/chrome-extension/offer-times.md) or [create a single-use link](/integrations/chrome-extension/single-use-links.md), when those actions are available. An Outbound Router starts a handoff rather than behaving like a personal booking URL. To share an outbound URL repeatedly, use a reusable outbound link made available by your admin. If a collection is empty or a link is missing, [check your account and access](/integrations/chrome-extension/troubleshooting.md). --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.distro.so/integrations/chrome-extension/share-links.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 `automate deployments from our CI pipeline` 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.