August 2026 release is live Read More
Breadcrumbs

MongoDB Atlas Onboarding

Why this matters: MongoDB Atlas usage is billed on its own schedule, separate from any cloud provider invoice — cluster tiers, storage, data transfer all accrue independently of whatever's running in AWS, Azure, or GCP. Without connecting it here, Atlas spend either lives in a spreadsheet someone updates manually, or doesn't get reviewed until the invoice lands. Connecting it means Atlas costs show up in Mavvrik's SaaS dashboards, with the same allocation and reporting tools available for your cloud spend.

This shows up differently depending on your role:

  • FinOps managers use this to catch Atlas cost growth (cluster upsizing, storage growth) before it's a surprise line item.

  • Data/platform teams do the actual onboarding — creating the service account and scoping its access correctly.

  • Finance leaders use this for chargeback when Atlas clusters are shared across multiple teams or projects.

Configuration steps

Step 1: Log in to MongoDB Atlas console and capture the Organization ID

  1. Log in to the MongoDB console as organization owner (https://account.mongodb.com/account/login )

  2. Click on the settings icon

Open MongoDB Atlas organization settings
Open MongoDB Atlas organization settings

  1. Capture the Organization ID

Copy the MongoDB organization ID
Copy the MongoDB organization ID

Step 2: Create a Service Account

  1. Create a service account

  2. Click on Access Manager

Open MongoDB Atlas Access Manager
Open MongoDB Atlas Access Manager

  1. Click on Add new > Click on Service Account

Add a MongoDB service account
Add a MongoDB service account
Select the Service Account option
Select the Service Account option

  1. Fill in the details and select roles as "Organization Read Only" and "Organization Billing Viewer."

Assign organization read-only and billing roles
Assign organization read-only and billing roles

We recommend selecting Client Secret Expiration as 365 days

Set the service account secret expiration
Set the service account secret expiration

  1. Click on create

  2. Capture the Client ID and Client Secret, which are used on Mavvrik for onboarding.

Copy the MongoDB client ID and client secret
Copy the MongoDB client ID and client secret

Step 3: Integrate into Mavvrik portal

  1. Go to Mavvrik portal and click on admin and then SaaS

  2. Click on +account and then select MongoDB

  3. Enter the details captured above and click connect

    • Organization id

    • Client id

    • Client Secret

Connect MongoDB Atlas in Mavvrik
Connect MongoDB Atlas in Mavvrik

Troubleshooting

  • If the account does not connect, verify the organization ID, client ID, and client secret entered in Mavvrik.

  • If a permission error appears, confirm that the service account has the roles specified above.

FAQs

What access does Mavvrik need to my MongoDB Atlas organization?
A service account with the Organization Read Only and Organization Billing Viewer roles — nothing beyond read access to organization and billing data.

How long should the service account's client secret be valid for?
Mavvrik recommends setting the Client Secret Expiration to 365 days when creating the service account.