Give each workflow the access it needs.
A connection identifies the caller. Vault and environment permissions define the resources that caller is allowed to use.
Authenticate the connection
Use the identity and authentication method approved for your workspace. Your administrator provides the sign-in instructions or connection configuration. The connector address is not an access credential.
Choose a resource scope
| Boundary | Example |
|---|---|
| Team | Platform engineering |
| Vault | Billing platform |
| Environment | Staging |
| Task | Consult connection metadata for a development task |
Use a staging resource for a staging task. Access to one vault or environment does not imply access to another. Ask the administrator to review the scope when a project, team or responsibility changes.
Review access over time
- Remove access that is no longer needed for the workflow.
- Review the connection when a team member leaves or changes role.
- Replace expired or revoked connection credentials through the approved process.
- Review resource access and changes in the workspace activity history.
If a request is denied, verify the intended identity and environment before requesting broader permissions. A retry with the same scope does not resolve a missing authorization.