Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-05

Approvers and access per environment

Who approves what goes to Production and what each person can do in each environment, with ready-made profiles.

On this page (3)

Approval#

In ETL/ELT → CI/CD → Approval and access:

  • Required approvals: from None to 3. The default is 1.
  • Approvers: tick who can approve. With no one ticked, any Production administrator approves. Save with Save approval.

Rules that always apply:

  1. Whoever requested the send never approves their own request.
  2. Approving requires administering Production.
  3. One rejection ends the send.

Ready-made profiles#

Each person gets a profile, which defines their role in each environment:

ProfileProductionDevelopment
Readerviewsno access
Developerviewsbuilds and requests the send
Owner-in-chargeadministers (can approve)builds and requests the send

The workspace owner has full access and does not change profile. A combination outside the profiles shows as Custom.

To bring someone new, invite them in Settings → Members. They show up in the CI/CD list and you choose their profile.

Development → Production connections#

A new pipeline goes to Production using the equivalent connection there. In the same section, choose, for each Development connection, which Production connection it represents. Without that choice, validation blocks the send.

Related links