Project Manager provides the interface for managing project spaces, projects, and assets. For Environment admins (Org admins), most environment configuration options are now available in Admin Manager and Monitor.

Open Project Manager from the waffle menu. The items in the navigation pane differ for Environment admins and standard users. The following image shows the navigation tree for an Environment admin:

In the Project Manager, the left navigation pane displays the tree of Project Spaces. Project Spaces provide a way to group related projects and set permissions for them. Each project space contains a shared folder and can include multiple individual projects. The shared folder directly under the Project Spaces label contains assets that are accessible from all project spaces and projects in the environment (Org). Similarly, the shared folder in a project space contains assets accessible from all projects in that space.

Create and manage project spaces

Environment admins are responsible for creating and managing project spaces. They set permissions for users and groups at the levels of the project space, the shared project, and individual projects. The available permission levels include:

• Read Only: Users can view assets.
• Read & Execute: Users can read and execute assets.
• Full Access: Users can read, write, and execute assets.
• Owner: Users can modify permissions on a project, change the ownership to another user, and perform all the actions allowed by the full access permission. The project creator is automatically assigned owner permissions.

Permission hierarchy and propagation

When a user or group has different permissions at different levels, the lowest permission level is enforced. For example, if a user has Full Access to a project space but one of the projects in that space has Read Only permission, the user will only have Read Only permission for all assets in that specific project.

Environment admins can choose to propagate permissions from the project space level to all projects in that space for a specific user or group. However, full access permission at the project level takes precedence over inherited permissions for the project space. To assign read, write, and execute permissions to an individual project space's shared folder, the Environment admin can explicitly assign Full Access to the user for that project space.

Moving projects and assets to another environment

Many SnapLogic customers use separate environments for development and production. The SnapLogic Git Integration enables you to promote projects and assets from one environment to another using Git operations. Without using the Git Integration, you can migrate projects and assets using the following methods:

• Project Export: Export all or selected assets to a .zip file for import into another environment (Org).
• Project Migrate: Migrate all or selected assets to another environment, leaving the original project unchanged.
• Asset Copy: Copy all, selected, or individual assets to another environment.