> For the complete documentation index, see [llms.txt](https://manual.formwise.ai/formwise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.formwise.ai/formwise/core-tools/toolsets/sharing-and-adding-toolsets.md). # Sharing & Adding Toolsets This resource will discuss sharing your Toolset links and adding new Toolsets from other users' links ## Sharing Toolsets Within your Toolset dashboard, navigate to **Embed & Share.** You can generate a link which allows any user with the link to create a copy of your Toolset if you share this link.

Once you have generated a link, anybody with this link can create a copy of your Toolset. The link is updated as you change your Toolset, so any changes made to the Tools or Toolset after you generate your link, will reflect your Toolset in its current state. ## Adding Toolsets from a link If you have received a link from another user, you can create a copy of that user's Toolset by navigating to the Toolset's popup.

You then click "Add from Link"

You can now paste the link you received into the "Link" box and once the link is validated, click "Next" and the Toolset and Tools will be copied into your account!

--- # 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://manual.formwise.ai/formwise/core-tools/toolsets/sharing-and-adding-toolsets.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.