> 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/when-to-use-shared-workspaces.md).

# When to Use Shared Workspaces

LogicNets' Shared Workspaces functionality allows you to set up a Designer workspace that can hold collaborative projects and that multiple Designer users can access. You check in projects to the shared workspace using version control, and Designer users with the appropriate read/write permissions can access these version-controlled projects and work on them, inspect them, or even make a local, uncontrolled version for their own purposes.

Shared workspaces might be useful to you when used under the following circumstances:

* You use LogicNets in multiple workspaces, multiple companies, and/or multiple installations, each supporting a group, team, or department with a different focus.
* You need some content to be shared across the group, team, or department.
* You also need some content to remain private/confidential/non-accessible to all users outside of the designated group/team.


---

# 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/when-to-use-shared-workspaces.md?ask=<question>&goal=<user_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.