Brex

Connect Brex to collect vendor procurement evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Brex:

   1. Sign in to dashboard.brex.com as an account admin or card admin.
   2. Go to Developer › Settings and click Create Token.
   3. Enter a token name and choose the level of data access the token needs (Safeguard only needs to read users).
   4. Click Allow Access to confirm the scopes.
   5. Copy the token right away; Brex will not show it again.

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

   Brex's public documentation does not cover every step.

   The fetched Brex authentication page confirms the click path, roles and one-time display but does not list the scope names shown on the Create Token screen, so the exact label for the users read-only scope (users.readonly in the API) is unverified. Tokens expire after 90 days of inactivity and stop working if the user who created them becomes inactive; they can be revoked from the developer dashboard.

   Source: developer.brex.com, checked 2026-10-07.

   The permissions Safeguard needs: users.readonly.

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

   Field	What to enter
   Access token	Required. Stored encrypted and never shown again.

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Brex 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

• Vendor Procurement 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