> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/advanced-topics/shared-workspaces/introduction-to-shared-workspaces.md). # Introduction to Shared Workspaces Available in v8.1+, *Shared Workspaces* is a platform component that allows for secure collaboration between multiple Designer users or groups of modelers, each working with their own content. It gives you the ability to efficiently share and jointly develop, manage, and deploy applications between workspaces. The Shared Workspaces function provides versioning capabilities at the project level. With it, you can set up one or more virtual content workspaces from which you can securely share projects with other internal or external users you invite for collaboration or joint access. Sharing provides read-only or read/write access to content, and the system combines versioning with a check-in/check-out capability that protects content integrity during multi-user collaboration. Shared workspaces allow specific users to load content into a dedicated workspace accessible by others within or outside of the same LogicNets installation. Content accessible from the shared space can be made available as read-only, or content can be shared subject to version control so users can securely collaborate on content. --- # 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://community-test.logicnets.com/release-9/platform-documentation/advanced-topics/shared-workspaces/introduction-to-shared-workspaces.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.