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 a shared folder Project and can contain multiple Projects. In Manager, the left navigation pane displays the the Project Spaces tree tree. The shared folder under Project immediately under Project Spaces contains 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.
...
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.
...
Org admins create and manage Project Spaces. They set permissions for users and groups at the Project Space, shared 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.
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 |
---|
Note |
Avoid creating your own directories in a Project Space because permissions do not propagate to them correctly. |
Creating a Project Space
Use Manager to As an Org admin, you can create a Project Space by clicking the drop-down icon next to Project Spaces in the left pane. in Manager:
In the left navigation, click the Project Spaces dropdown menu:
Select Create Project Space.
Enter a name.
Click Create.
The new Project Space is inserted in alphabetic order of the name into the list of Project Spaces. Once a Project Space is created, you can set permissions for it and create and import Projects into it.
...
displays in the tree in alphanumeric order.
Info |
---|
More than 1000 project spaces in an org Org or more than 1000 projects in each project space , then that may can create performance and usability issues. |
Using Expression Libraries
...
Assigning Permissions for a Project Space or Project
As an Org administrator, you can an Org admin assign permissions to any user or group at the Project 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 levelas follows:
Click the
...
dropdown arrow for the Project Space or the Project:
The context menu opens:
Click Permissions.
From the Add dropdown list, select a user or a group. For Project Space permissions, check Propagate permissions to grant the same permission for all Projects in the Project Space:
From the permissions dropdown menu, select the permission level.
Click Save.
Add more permissions, or if finished, click Done.
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.
Info |
---|
Info |
After you propagate permissions, the user or group displays only in the Permissions dialog for the shared folder, not for the individual projects. Although they don’t show uin the Permissions dialog for individual projects, they have the permission granted at the Project Space level. |
Deleting a Project Space
...
You must
...
be an Org
...
admin or
...
the Project Space owner to
...
delete a Project
...
Space.
...
Deleting a Project Space removes all its assets from SnapLogic.of its Projects and Assets. Deleted items first go in the Recycle bin, where you can restore or permanently delete them. Learn more about the Recycle Bin
To delete a Project Space:
In the Manager left navigation pane, click
...
the
...
dropdown icon next to the Project Space name:
From the dropdown menu,
...
select Delete. A confirmation box displays:
Click Delete.
Restoring or Permanently Deleting Project Spaces and Projects
Org administrators can restore deleted Project Spaces and Projects from
...
See Also
Dashboard Pipeline Wallthe recycle bin or permanently delete them.
To restore an item:
From the left navigation, select Recycle Bin:
Click Project Folders to list deleted Project Spaces and Projects:
Select the item to restore.
In the toolbar, click Restore:
In the confirmation dialog, click Restore.
To permanently delete an item, follow Steps 1-3, but click Permanent Delete instead:
...