Skip to main content

​
Overview

nOps uses your MongoDB Atlas Organization ID and organization API keys to bring Atlas spend into Inform across the projects you grant access to. Keys are stored securely, validated before save, and are not shown again after you connect.

​
Prerequisites

  • MongoDB Atlas organization administrator access
  • API keys with Organization Billing Viewer at the org level and Project Read Only on each project you monitor
  • nOps organization administrator access
Only admins and owners can connect, re-validate, or disconnect. Members see Admin Only on connectable cards.

​
Step 1: Find your Organization ID

The Organization ID is a 24-character identifier for your Atlas organization.
  1. Open the MongoDB Atlas Organizations page.
  2. Select your organization.
  3. Click Settings in the left menu.
  4. Copy the Organization ID exactly as shown (organization settings, not project settings).

​
Step 2: Create API keys

  1. In Organization Settings, open Access Manager → Applications.
  2. Click Add new → API Key.
  3. Name the key (for example nOps Integration).
  4. Assign the Organization Billing Viewer role.
  5. Copy the Public API key and Private API key — the private key is shown only once.
If your organization uses an IP access list for the Atlas Administration API, allow 52.11.169.55 so nOps can validate and sync credentials. Without this, connect or re-validate may fail even when keys are correct.

​
Step 3: Configure project access

Repeat for each project you want in Inform:
  1. In Organization Settings, click Projects and select a project.
  2. Open Access Manager → Project Access.
  3. Click Invite to Project, select your integration API key, and grant Project Read Only.
  4. Confirm the invitation.
The key needs both Organization Billing Viewer (org level) and Project Read Only (per project).

​
Connect in nOps

​
Where to open MongoDB

  • To connect for the first time — go to Settings → Integrations and click the MongoDB card.
  • To manage an existing connection — go to Settings → Account Status → Connected apps and click the MongoDB chip to re-validate or disconnect.

​
Connect steps

  1. Click the MongoDB card or chip.
  2. Enter Organization ID, Public API key, and Private API key.
  3. Click Connect.
nOps validates credentials against the Atlas API before storing them. Validation can fail if the IP access list blocks nOps — add 52.11.169.55 in Atlas if required.

​
Manage your connection

Administrators can Re-validate or Disconnect from the modal. Action required may mean revoked keys, wrong Organization ID, missing project access, or IP restrictions.

​
Troubleshooting

  • Validation failed — check Organization ID, both keys, Billing Viewer + Project Read Only, and IP allowlist 52.11.169.55.
  • Organization ID mismatch — keys may be valid but not authorized for the Organization ID you entered.
  • No billing data — allow up to 24 hours after connect; confirm keys are invited to all relevant projects.
  • Multiple organizations — use separate API keys and separate connects per organization.

​
Security

Treat the private API key like a password. Rotate in Atlas if it may have been exposed.