> 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-projects-from-a-shared-workspace.md). # Working with Projects from a Shared Workspace Once your permissions are configured to work on a project in a shared workspace, you can copy shared projects to your local Designer. See Getting Started with Shared Workspaces for information on configuring access to a shared workspace. ## Copy Shared Projects to the Local Designer To view or edit a project in a shared workspace, you must copy the project from the configured *workspaces* subfolder to the *projects* subfolder of your local Designer workspace. You do this the same way you copy local projects. * In the workspaces subfolder, click on the name of the project you to copy from the shared workspace. * In the project tree tools, click the copy icon. * Select a destination folder or subfolder in your *projects* folder * Click on the paste icon ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-30e71543a0cd056388a1083e1ec0f1549d518b05%2Ff16b6404-daf5-4f61-86f4-d1f5606d163a.png?alt=media) The full project now exists in your local designer workspace. From here, you can view it, check it out, or modify it. You can also unlink it meaning you have a copy that is no longer in version control. ## View a Version-Controlled Project You can view a project that is in a shared workspace if your permissions are limited to *remote-read*. With these permission rights, you can: * Inspect all project settings, logicnets, nodes, parts and parameters, and resources such as images, content references, and CSS. * Run the project in test mode. Note: Even though your permissions are "remote-read" the process of running the application in test can update any application and/or session tables and changelogs associated with the project. * Access and run published copies of the project. ## Edit a Version-Controlled Project You can edit a shared project if your permissions include *remote-write* or *admin.* The step numbers in this section relate to the image above. 1. Click the project details tab. 2. Select ***Check out Revision**.* 3. Make edits to the project logicnets, resources, and other details, as appropriate. 4. Click ***Check In Revision** .* And status and notes. 5. You can also unlink the project to remove the version control from this local copy. This is useful for doing local exploratory work prior to working on the controlled version. ## Change Permissions What action you get to take in relation to a shared project or shared workspace depends on permissions set in the AccessManagement function, and these permissions can be changed easily. If your permissions are revoked or downgraded from *remote-modify* to *remote-read*, it does not remove the link to the shared workspace or remove the local copy. * Downgrading permissions to *remote-read* has the following impact on the local copy of the project: * You can still view it and test it. * You can update it to the latest version. * You can unlink it to create an editable version that is not version controlled. * You cannot check it out or, if it is currently checked out, you can no longer check it in. * Downgrading permissions to remove remote access has the following impact on the local copy of the project: * You can still view and test it. * You can unlink it to create an editable version that is not version controlled. * You cannot update it to the latest version. * Once you delete it from your local projects list, you cannot reinstate it. It will not show in the Shared Workspaces project list. --- # 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-projects-from-a-shared-workspace.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.