# MongoDB Atlas temporary access

[Temporary access overview](/docs/concepts/temporary-access) covers target setup, connection methods, and credential handling.

Atlas targets create database users through the Atlas Administration API. This
is separate from the [direct MongoDB integration](/docs/guides/dynamic-mongodb), which uses the database wire
protocol. Atlas configuration fixes the project, roles, and allowed clusters:

```json
{"provider":"mongodb-atlas","executor":"in_do","projectId":"0123456789abcdef01234567","roles":[{"roleName":"read","databaseName":"events"}],"clusters":["analytics"]}
```

Supply encrypted JSON with an Atlas service account's `clientId` and `clientSecret`.
The account needs the project's database-user management permissions (such as
Project Data Access Admin); its API access list must permit the broker's network.
This integration uses service-account OAuth, rather than legacy Digest API keys.
Register and mint in the dashboard or with `seekrit dynamic`.

Output contains `username`, `password`, `authDatabase` (`admin`), and `projectId`.
Use those with the selected cluster's MongoDB connection string. The broker sets
Atlas's `deleteAfterDate` and also deletes the user on revoke/expiry. Lifetimes
are limited to seven days. Creation and deletion propagate through Atlas, so
credentials may not become usable or invalid immediately; existing sessions
are not forcibly terminated by Seekrit.

See the [CLI reference](/docs/reference/cli) and [API reference](/docs/reference/api) for commands and endpoints.
