In this article

Project spaces are an additional level added above projects to help you better organize your pipelines. 

Each Project Space contains a shared project to contain assets shared between the projects of that Project Space. There is also a global shared folder above the Project Spaces that is accessible to the entire org. 

When moving or copying pipelines, related assets are checked for within the pipeline's project first, then the Project Space's shared folder, then the global shared folder.

Project Spaces in Designer

In Designer, Project Spaces are supported in:

• the Pipeline Catalog
• when creating/importing/moving pipelines
• when selecting accounts or files.

Project Spaces in Manager

In Manager, org admins can create Project Spaces from the Project Spaces drop-down within the left pane.

 Once a Project Space is created, you can:

• create or import projects
• set permissions from the Project Space

Setting Permissions

Permissions can be set at the Project Space level to limit access to project assets to avoid unwanted changes/deletions. Org administrators can assign permissions to any user or group at the project space level or at project level.. Project owners can assign permissions to users or to any group to which they belong. 

The following permission types are supported:

• Read Only: Read the assets within the project.
• Read & Execute: Read and execute the assets inside the project.
• Full Access: Read, write, and execute inside the project.
• Owner: Modify permissions on the project, change the ownership to another user.

Permissions at a higher level in the asset hierarchy are automatically applied to all lower-level assets. For example, a Read Only permission applied at the project space level will automatically apply to all projects within the project space.

Project Spaces in Dashboard

In Dashboard, you can filter Executing Pipelines and Pipeline Execution History by projects in any Project Space.