Environment access
There are three access levels for Designer environments: Admin, Read Only, and No Access. You can set one of these access levels as the default for a given environment. This access level is then granted to all existing and future users who join a project until an admin edits a user's access level.
Users assigned the Admin role for a project have the ability to adjust access levels for specific users, granting them either higher or lower permissions than the default access level established for the environment. Project admins can further modify these settings by editing the intended environment.
When an environment is modified, all users with the default access level will be automatically and immediately updated to the new default environment access level.
Default environment access is defined in three areas:
- When you create a project.
- When you edit an existing environment.
- At the user level.
For the full list of access level permissions and their settings, read Environment permissions.
Editing access levels on existing environments
To edit the environment access levels on an existing environment, use the following steps:
- In your project, click the Environments tab.
- Click ... next to the environment you want to modify.
- Click Edit Environment.
- Scroll down to Default environment access.
- Use the drop-down menu to select the relevant access level for the intended environment. Choose Admin, Read Only, or No Access.
Edit user environment access
All users in a project automatically inherit the default environment access level on the environment—this includes any existing users of a project at the time that the project is created, and any users that are subsequently added to the project. If the default environment access level is changed by a user with the Admin role, then all users will automatically inherit the new default setting immediately.
Any user with the Admin role for a project can optionally set explicit access for individual users. To do this:
- In your project, click the Environments tab.
- Click ... next to the environment you want to set the explicit access on.
- Click Edit user access.
-
Use the Access drop-down menu to choose the access level for the individual users.
Note
To find specific users quickly, search by name or email address.
-
Click Save.
The new access will take effect immediately.
Environment permissions
The three roles Admin, Read only, and No Access, have specific permissions for the following features:
Note
Users assigned the Super Admin role are always granted the Admin role for all environments in that account.
Function | Admin | Read only | No Access |
---|---|---|---|
Validate pipelines | ✅ | ❌ | ❌ |
Sample pipelines | ✅ | ❌ | ❌ |
Run pipelines | ✅ | ❌ | ❌ |
Publish pipelines | ✅ | ❌ | ❌ |
View Executions | ✅ | ✅ | ❌ |
Create Schedules | ✅ | ❌ | ❌ |
View Schedules | ✅ | ✅ | ❌ |
Edit Schedules | ✅ | ❌ | ❌ |
Delete Schedules | ✅ | ❌ | ❌ |
View lineage | ✅ | ✅ | ✅ |