Qovery

Connect Qovery to collect cloud infrastructure evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Qovery:

   1. Log in to the Qovery Console (https://console.qovery.com).
   2. Go to Organization Settings › API Tokens.
   3. Click Generate Token.
   4. Give the token a descriptive name and set its permissions to the lowest role that reads members.
   5. Copy and save the token: it is displayed only once.

   Qovery shows the secret only once, so copy it before you leave the page.

   Qovery's public documentation does not cover every step.

   Qovery's built-in roles are Owner, Admin, DevOps, Billing Manager and Viewer; the permissions matrix gives Manage members & roles only to Owner and Admin, and Viewer has read-only access to all organization resources. The docs do not say which token role can list members read-only, or the exact name of the role picker on the token screen. Where the Console shows the Organization ID was not found.

   Source: qovery.com, qovery.com, checked 2026-10-07.

   The permissions Safeguard needs: the lowest role that reads members.

2. On Compliance › Connectors, open Qovery, click Connect, choose API token and fill in:

   Field	What to enter
   API token	Required. Stored encrypted and never shown again.
   Organization ID (optional)	—

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Qovery and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Cloud Infrastructure connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks