> 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/workspace-role-assignment.md).

# Workspace Role Assignment

Users with access to the Access Management functionality can configure a shared workspace for access by user groups with different permission levels. The table below details permission levels available for both local and shared workspaces. Note that, by default, user groups with access to a local workspace have *full-access* rights.

| Role                                                 | Workspace Applicability | Permissions Granted                                                                                                                                                                                                                                                                                                             |
| ---------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| local full-access                                    | Local only              | <p>Default workspace role for all groups starting from Release 8.0 on, which gives full read/write and publish rights.<br>This is not shown explicitly in the workspace role table for a given group, but it can be added.</p>                                                                                                  |
| local read-only                                      | Local only              | Grants visibility to view local project details, logicnets, resources, test projects. With this role assigned, it is not possible to edit any aspect of projects, and there is no access to published packages, start codes or URL links with this role.                                                                        |
| local read-modify                                    | Local only              | <p>Grants ability to view and edit local project details, logicnets, resources, test projects.<br>With this role assigned, it is not possible to inspect existing published package links or publish/republish existing or new projects.</p>                                                                                    |
| local publish-and-deploy                             | Local only              | Grants ability to see published packages, startcodes and URLs, to republish existing projects and publish new projects in addition to viewing/editing local project details, logicnets, resources, test projects.                                                                                                               |
| <p>local admin-access<br>(local version control)</p> | Local only              | <p>Grants full read/write access to local projects AND gives the ability to unlock a version-controlled <strong>local</strong> project that has been checked out by another local user.<br>This does NOT allow for unlocking of version-controlled projects that are sourced from other <strong>shared</strong> workspaces.</p> |
| remote read-only                                     | Shared only             | For use with shared workspaces only. Grants visibility to view project details, logicnets, resources, test projects, and see/run published versions.                                                                                                                                                                            |
| remote read-modify                                   | Shared only             | For use with shared workspaces only. Grants visibility to view and edit project details, logicnets, resources, test projects, and see/run published versions.                                                                                                                                                                   |


---

# 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/workspace-role-assignment.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.