> 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/working-with-shared-workspaces.md).

# Working with Shared Workspaces

One or more remote workspaces may be accessible via your Designer. Clicking on a remote workspace in the workspaces folder of the Explorer panel in the Designer (highlighted in yellow below) will bring up the details of that workspace.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-d8a6df4079a1a358154a19d30136bb50b8a0badb%2F87b11752-9817-4499-8a70-3eaad58b1396.png?alt=media)

### Workspace Details

* **Workspace URL** consists of a "root" and "repository" component. The part of the URL before Repository indicates the source URL for the shared workspace. In the example above, the shared workspace is part of the [*support.logicnets.com*](http://support.logicnets.com) installation and *community\_portal* instance or company. You may (or may not) have been given access to this installation and instance/company. Contact your Access Management/System Administrator for more information on this.
* **Workspace Name** is the name of the Designer workspace on that installation that is being shared. In the example above the shared Designer workspace is called Community Portal. Note that this may differ from the name in the workspaces folder (as shown in yellow) which is the "local" name chosen when the remote workspace was first shared to your workspace
* **Permissions** shows the extent of access rights granted to users in this workspace. For a full list of permissions, see [this](/release-9/platform-documentation/advanced-topics/shared-workspaces/workspace-role-assignment.md) article. The most common permissions are:
  * none: you will not be able to see any projects within the Shared Workspace
  * remote-read: you will be able to inspect the project, create a new copy locally unlinked to the shared workspace version, but you will not be able to check out the project to make edits
  * remote-modify: you will be able to inspect the project, create a version-controlled copy locally that you can check out, edit and check in changes

If you think you do not have the correct permissions for a shared workspace, contact your Access Manager or SystemAdministrator.

Once you have access to project(s) in a shared workspace, see [Working with Projects in a Shared Workspace](/release-9/platform-documentation/advanced-topics/shared-workspaces/working-with-projects-from-a-shared-workspace.md) for next steps.


---

# 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/working-with-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.