> ## Documentation Index
> Fetch the complete documentation index at: https://docs.draftt.io/llms.txt
> Use this file to discover all available pages before exploring further.

# MongoDB Atlas

Connect your MongoDB Atlas organization or projects to Draftt to detect version gaps, monitor performance risks, and stay ahead of patching.

## Prerequisites

* A MongoDB Atlas account with permissions to create API keys at the Organization or Project level
* Access to the Draftt dashboard (**Integrations > MongoDB Atlas**)

## Setup

Draftt supports connecting at the **Organization** or **Project** level. Organization-level access covers all projects underneath it.

<Steps>
  <Step title="Navigate to your organization">
    Log in to [MongoDB Atlas](https://cloud.mongodb.com). Select the organization you want to integrate with Draftt by clicking its name.
  </Step>

  <Step title="Create an API key">
    1. Click **Access Manager** (or **Applications** depending on your Atlas version)
    2. Click **Add New** and select **API Key**
    3. In the **Description** field, enter: `Draftt Integration - Organization`
    4. In **Organization Permissions**, select **Organization Read Only**
    5. Click **Next**
  </Step>

  <Step title="Enter the keys in Draftt">
    Copy the generated **Public Key** and **Private Key**. Back in the Draftt setup dialog, paste both keys and click **Create**.

    <Warning>
      The Private Key is only shown once. Make sure to copy it before closing the dialog.
    </Warning>
  </Step>
</Steps>

## What Draftt Reads

Draftt's API key has **read-only** access. It cannot create, modify, or delete any resources in your MongoDB Atlas environment.

Draftt monitors cluster versions, configuration settings, backup policies, and maintenance windows across your Atlas deployments.

## Verifying Your Connection

After setup, return to **Integrations > MongoDB Atlas** in Draftt. Each connected organization or project shows a status:

* **Healthy** -- Draftt can access your Atlas data as expected.
* **Unhealthy** -- Check that the API key has not been revoked and has Organization Read Only permissions.

## Troubleshooting

**Authentication fails:** Verify the Public Key and Private Key are correct. Confirm the API key has not been deleted from Atlas.

**Missing clusters:** If you connected at the Project level, only clusters in that project are visible. Connect at the Organization level for full coverage.

**IP access list errors:** MongoDB Atlas may require API key access from specific IPs. Check your Atlas API access list settings if connections fail.