> 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-logicnets-community-portal-shared-workspace.md).

# Adding LogicNets Community Portal Shared Workspace

Any Designer account can have access to the LogicNets Community Portal Shared Workspace. This shared workspace contains all of the How To Guides, example projects and part demonstrations in the Community Portal. Having access to them via the Designer allows you to run the projects, inspect them to see how they work, copy parts into your own project and even create a copy that you can edit with your own changes.

If your Designer account does not already show the shared workspace, below are the configurations required. There is no additional license requirement to read and work with this shared workspace.

### LogicNets Community Portal Shared Workspace Configurations

The following three configurations are required:

1. \[Shared Workspace Root URL] currently <https://support.logicnets.com>
2. \[Shared Workspace Company] currently community\_portal
3. \[Shared Workspace Designer Name] currently CommunityPortal

Enter the configurations 1-3 acording to the screenshots below.

#### System Configuration Package

* Enter the Shared Workspace Root URL (1) in the URI field of Outbound Webservice Security
* Click SAVE before exiting from this package

  ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-75c7e7a3f0438bc60569986543de0ad8731ee2ce%2F76e14f14-b9d0-4354-b422-1576ae369dfc.png?alt=media)

#### Your Designer Workspace

* Click on the New Shared Workspace icon (top left)
* Enter the configurations from 1, 2 and 3 above
* Enter your own preferred name for the workspace - this name is what will appear in the Designer (see image at top of article)
* Click on the LINK button

  ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-5bed213effd01a179c4bd3ef209267b3ff654ac3%2F4913b47a-5477-4f0c-8014-a8b4cf8f7e3d.png?alt=media)

### Working with the LogicNets Community Portal Shared Workspace

Once you have access to the shared workspace you can copy any project to your projects folder to inspect, test etc. To edit your own copy of any project, copy and then UNLINK it to create a non-version controlled copy that is fully accessible to you.

Periodically, LogicNets Support will add new projects and/or update existing projects. These edits will be automatically updated in your account. For any given project, inspect the revision notes to see what changes have been made.

For more information on working with shared workspaces in general, see [this](/release-9/platform-documentation/advanced-topics/shared-workspaces/working-with-projects-from-a-shared-workspace.md) article.


---

# 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-logicnets-community-portal-shared-workspace.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.
