> 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/adding-a-shared-workspace-to-your-designer.md). # Adding a Shared Workspace to your Designer ## Description LogicNets' Shared Workspaces functionality allows you to set up a Designer workspace that can hold collaborative projects and that multiple Designer users can access. This article describes the steps for how to set up shared workspaces and get started using them: * Set up a shared workspace and permissions * Load content to a shared workspace * Set up local access to a shared workspace * Work with projects in a shared workspace **NOTE: For specific instructions on how to set up the Community Portal shared workspace go to** [**this**](/release-9/platform-documentation/advanced-topics/shared-workspaces/adding-logicnets-community-portal-shared-workspace.md) **link.** ## Set Up Workspace and Permissions This section walks you through how to create a workspace and assign permissions to those users who can load, view, and edit projects in the shared workspace. To perform these steps you must have access rights to the Access Management module. 1. Navigate to the *Workspaces* page in Access Management (A) and create a new workspace (B). In the image below we name it TeamVault. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-973b2a94aa74feaa9d35c5cda14c83e1eab2a537%2Ffa71198a-f0c1-4a51-80a0-459486377ad8.png?alt=media) 2. With the image below as an example, create a user group (A and B) and add to it the users (C) who are allowed to load initial content. You can also use an existing group. * Add the shared workspace to the group's dashboard (D). The system places the workspace on their landing page. * (Optional) Add a description for the group (E). * Ignore (F) - this step has been incorporated into the workspace roles in v8.3 on. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-18d28c575887e27c46f9f08df685adc87ad9bb9a%2F5bf337d2-21aa-4800-8f79-9b78eb72d2bb.png?alt=media) Note: The dotted line indicates some options removed from screenshot for simplicity. 3. Create user groups using existing groups containing users who are allowed to view and/or modify the content from their own Designer. For each group, after creating and saving the group name, click *Modify* and perform the following steps: * DO NOT add the shared Designer to the Workspaces on Dashboard, because users will access the shared workspace using API calls from their local workspace. * Add *RepositoryAPI* as a group role with readonly rights. * In the *Workspace roles* section, add a workspace (A), choose the name (B), and choose one or more roles for the group (C). ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-1eb7674c75a5f47dca1ef2c3567a44c40d51e372%2Fd1c60314-8545-45ca-851d-074f910dde5c.png?alt=media) * For viewing rights, select *remote-read.* * For editing and viewing rights, select *remote-modify.* * For admin rights, select *admin* role. See [Workspace Role Assignments](/release-9/platform-documentation/advanced-topics/shared-workspaces/workspace-role-assignment.md) for more detailed notes on the role choices. ## Load Content to a Shared Workspace Users in the appropriate group can load content to share using the steps below for each shared project. Projects that are not checked in are not available for others to view or edit. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-1cbfe3c36ddacca0dfbf47fb3352f196192f5403%2Fc68744f7-7c6f-432a-8298-ad9214dc0aae.png?alt=media) Create or import the project to the Shared Workspace Designer. See A in the image above. 1. Verify the Project Details. * Click ***Modify*** (B) to edit the Author, Owner, Version, and Description fields, which are visible to others when this project is shared. * Click ***Create Revision*** (C). - Select a status option: *Draft*, *Beta*, or *Released*. - Enter revision notes that explain the changes to the revision. This could be "Initial shared version" or a list of the features added, and defects fixed and is available for others to see what was included in the latest revision versus earlier versions of the project. - Click ***Submit*** to save the revision to the shared workspace. This makes the project visible to other users with the correct permissions. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-dee259604e12e9b243b3d0844be513693d29bdd7%2F857b3cad-bb58-452f-aa94-27128b98e900.png?alt=media) ## Access a Shared Workspace Users with the correct permissions can set up access to the shared workspace from their local Designer workspace by following the steps below. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-f793558ff4acdd5c262ea1745b7e43035c417672%2F63696f36-555b-4d8b-ba44-1e3678702def.png?alt=media) 1. From your Designer, click the *workspaces* folder. 2. Click the "*Link to Shared Workspace*" icon at the top of the project tree. 3. Accept the default URL Root, unless you are sharing content from a different installation or company \* 4. Enter the exact name of the Shared Workspace, which your Access Management Administrator can provide. 5. Use the prefilled name or enter one of your choosing. 6. Click ***Link**.* When successful, the name of the shared workspace appears in your *workspaces* folder, along with details of the permissions. Expand the shared workspace icon to reveal the list of shared projects. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-fe2a2820c51dcb33c3687445ffcb9d28bd1768db%2F58fd3595-dbbc-41c4-a9f5-d744c8e8bc41.png?alt=media) ### Bookmarking Workspace URLs In Release 8.4+ workspace URLs can be bookmarked by using the root-company-designer-workspace name as follows: * *https\://\[root]/\[company]/designer/\[workspace\_name]* Note that everything from ?\_session=123.... should be removed in the bookmark ### Troubleshooting If the system is not able to link to the shared workspace you will see an error code and error message. See [Troubleshooting Version Control and Shared Workspaces](/release-9/platform-documentation/advanced-topics/shared-workspaces/troubleshooting-version-control-and-shared-workspaces.md) for information on troubleshooting. ### External (Different Root URL) Workspaces \* if you are trying to set up a shared workspace from a different root URL (a partner or other installation) you will need to whitelist the directory before these steps. See this article for more information on whitelisting. [https://community.logicnets.com/t/g9y6wz5](/release-9/platform-documentation/system-administration/security/outbound-api-security.md) --- # 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/adding-a-shared-workspace-to-your-designer.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.