RingCentral

Connect RingCentral to collect identity & sso evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In RingCentral:

   1. Log in to the RingCentral Developer Console and select Apps from the left-hand navigation.
   2. Click Create App, select the REST API App app type, and click Next.
   3. Under the Auth section, select JWT auth flow.
   4. Save and create the app, and note its client ID.
   5. Create the JWT: hover over your name in the upper right-hand corner, select Credentials, and click Create JWT. Under What apps are permitted to use this credential?, check Only specific apps of my choice, paste the app's client ID, click Add app, then click Create. Use a dedicated service user for this, not an employee's login.
   6. Present the JWT to RingCentral's Auth API, which responds with an access token, and paste the access token into Safeguard.

   Where to find the other values:

   • Environment (optional): Production or Sandbox: the environment your app's credentials were issued for in the Developer Console.

   RingCentral issues this credential through its API or its support team, not through its admin screens.

   RingCentral issues access tokens through an API call (the app presents the JWT to the Auth API), not a UI button; they are short-lived, so collection stops when the token expires. The fetched pages do not name an app permission such as ReadAccounts, a Security section, the token endpoint, the token lifetime or whether the JWT is shown only once, so those were removed. JWTs belong to a user, so the token acts with that user's account permissions; RingCentral recommends a dedicated service user.

   Source: developers.ringcentral.com, developers.ringcentral.com, checked 2026-10-07.

   The permissions Safeguard needs: ReadAccounts.

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

   Field	What to enter
   Access token	Required. Stored encrypted and never shown again.
   Environment (optional)	—

3. Click Connect with token.

Frameworks

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

• Identity & SSO 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