In this article
Table of Contents | ||||
---|---|---|---|---|
|
Overview
Project Spaces provide a way to group related Projects and set permissions for them. Each Project Space has a shared folder Project and can contain multiple Projects. In Manager, the left navigation pane displays the Project Spaces tree. The shared folder Project immediately under Project Spaces contains Assets that are accessible from all Project Spaces and Projects in the Org. The shared folder Project in a Project Space contains Assets that are accessible from all Projects in that Space.
...
Org admins create and manage Project Spaces. They set permissions for users and groups at the Project Space, shared folder Project, and Project level. The following permission levels are available:
Read Only: View Assets.
Read & Execute: Read and execute Assets.
Full Access: Read, write, and execute Assets.
Owner: Modify permissions on a Project, change the ownership to another user, plus all of the above. The Project creator has Owner permissions.
...
When a user or group has different permissions at different levels, the lowest permission level is enforced. For example,
...
a user might have Full Access to a Project Space, but if it contains a Project with Read Only permission, the user only has Read Only permission for all Assets in that Project.
When assigning permission to a Project Space, Org admins can choose to propagate the same permission to all Projects in the Space for that user or group. To assign read, write, and execute permissions to an individual Project Space shared folder, the Org admin can also explicitly assign Full Access to the user for that Project Space.
Note |
---|
Avoid creating your own directories in a Project Space because permissions do not propagate to them correctly. |
Creating a Project Space
As an Org admin, you can create a Project Space in Manager:
...