Scopes
Hint
The scope describes who can use the integration to define new actions and edit actions that use an existing integration
Warning
The scope does not describe who can trigger the actions that use the integration. For example, if you define an S3 deployment with a private scope, all users with permissions to run the pipeline will be able to upload files to the defined S3 bucket. However, only the user who has added the integration will be able to edit its details (e.g. change the deployment bucket in the S3 action).
Types of scopes
There are four types of integration scopes. Each scope defines who can add and edit actions using the integration:
- Private – restricted to the owner of the integration. The scope can be further limited to a specific project.
- Everyone – restricted to the members of the workspace in which the integration was defined. The scope can be further limited to a specific project (recommended for YAML configuration).
- Administrators – restricted to the admins of the workspace in which the integration was defined. The scope can be further limited to a specific project.
- Administrators + Group – restricted to admins and a selected group of users in the workspace in which the integration was defined. The scope can be further limited to a specific project (for example, back-end developers in a back-end project).
Last update:
Sep 13, 2024
Sep 13, 2024