In this article
...
Every Project Space has a shared folder where assets are shared between the various Projects within that Project Space. The global shared folder is accessible to all the Projects and Project Spaces within the Org.
Unlike the global shared folder, where all users in the Org have read and execute permissions, an Org Admin has to add users to a Project Space and then assign permissions to the shared folder in that Project Space. Users added to the shared folder in Project Spaces automatically get read and execute permissions, which the Org admin can later update. For read, write, and execution permissions to a Project Space shared folder, an Org admin must explicitly assign full access to the user for that Project Space.
You can create and import Projects within Project Spaces to which you have at least Write permissions. When you move or copy Pipelines across Projects, SnapLogic checks for the related assets first within the Pipeline's Project, then in the Project Space' shared folder, and finally in the global shared folder.
| Info |
|---|
You must have Org Administrator access to create and manage Project Spaces. |
...
Assigning Permissions for a Project Space
As an Org administrator, you can assign permissions to any user or group at the Project Space or Project level to limit access to project assets and define the actions users can perform.
To assign permissions at the Project Space level:
...
To assign permissions at the Project level, click on the drop-down icon next to the Project name and perform the steps mentioned above.
Supported Permission Types
- Read Only: Read the assets within the Project.
- Read & Execute: Read and execute the assets within the Project.
- Full Access: Read, write, and execute the assets within the Project.
- Owner: Modify permissions on the Project, change the ownership to another user, plus all of the above.
...