MongoDB Atlas

Connect Atlas organization users, teams, API keys, and database access to Superviso.

The MongoDB Atlas connector supports Identity & Access collection for an Atlas organization. Collection options can include organization users, database users, and organization API keys.

Required values

  • API Public Key and API Private Key
  • Organization ID for the Atlas organization Superviso should read

Required access

Grant the API key the Organization Read Only role. Select only the organization-user, database-user, and API-key collection options required for your review scope.

Use a dedicated organization API key rather than a personal credential.

Before you start

Create the credentials listed above in the provider’s administration tools.

Configure in Superviso

  1. Open Settings → Connectors and choose Add connector.
  2. Select MongoDB Atlas from Provider.
  3. Associate the intended asset, or use the new-asset option when appropriate. Enable only the supported synchronization options you need.
  4. Enter API Public Key, API Private Key, and Organization ID. Choose the required Organization Users, Database Users, and API Keys filters.
  5. Recheck the required privileges, scope, and filters, then choose Create connector. Resolve any validation errors shown by the form.
  6. Open the saved connector, choose Sync connector when available, and confirm the synchronization scope.
  7. Open Logs, wait for execution to finish, and inspect the result and any errors. Open the relevant Identities, Privileges, or Resources page for the enabled integration to verify collected records.
Unsaved MongoDB Atlas connector setup with synchronization options and blank credential fields.
Select MongoDB Atlas and review its supported options before entering your own credentials. Select the image to view it full size.

Expected outcome

The connector is saved for MongoDB Atlas with the intended integration and collection scope. Synchronization logs show progress, results, and imported records.

If setup or synchronization fails

Check the exact account or organization identifier, required form values, credential validity, granted access, and selected filters. Inspect the failed log’s details before retrying. If only some records are missing, check their scope and provider permissions. For synchronization status and source-managed fields, see Connectors and synchronization logs.

Back to Providers

Screenshot

Scroll to inspect the image, or choose Fit image to see the whole screen.