Join us Sept 17 at .local NYC! Use code WEB50 to save 50% on tickets. Learn more >
MongoDB Event
Docs Menu
Docs Home
/
Atlas
/ / /

Manage Organization Settings

To perform any of the following actions, you must have Organization Owner access to Atlas.

Organization Owners can configure the absolute and idle session timeouts for all users of an organization to comply with security and certification policies.

The absolute session timeout specifies the maximum duration a user can remain logged in to the Atlas UI without re-authenticating. The idle session timeout specifies the maximum duration a user can remain inactive before Atlas logs them out.

Note

This feature is in Public Preview. The feature and the corresponding documentation might change at any time during the Preview period. To learn more, see Preview Features.

  • If a user belongs to multiple organizations, their session inherits the shortest idle and absolute timeouts from across all of them. For example, a user's session combines the shortest absolute timeout from one organization with the shortest idle timeout from another. To view the timeouts that apply to you, see the Personalization page.

  • Two minutes before an idle session expires, Atlas displays a message allowing the user to continue the session.

  • Timeout configurations apply only to the Atlas UI. They do not affect:

    • account access through API keys or service accounts.

    • sessions where users log in to developer tools like Compass, the Relational Migrator, or the Atlas CLI using their Atlas credentials. A fixed 12-hour session timeout applies instead of the custom values.

    • sessions where users log in through MongoDB Charts and Atlas App Services directly.

    • MongoDB SSO-linked services such as MongoDB University and the Support Portal. These services use a 12-hour session timeout.

    Important

    For the tools and services listed above, sessions might still expire in less than 12 hours if your main Atlas web session ends.

1

WARNING: Navigation Improvements In Progress

We're currently rolling out a new and improved navigation experience. If the following steps don't match your view in the Atlas UI, see the preview documentation.

  1. If it's not already displayed, select your desired organization from the Organizations menu in the navigation bar.

  2. Click the Organization Settings icon next to the Organizations menu.

    The Organization Settings page displays.

2
  1. In the Configure Session Timeout section, click .

  2. Specify the absolute and idle session timeouts.

    The absolute session timeout must be greater than or equal to the idle session timeout.

    For Atlas, limits include:

    Session Timeout
    Default
    Minimum
    Maximum

    Absolute

    12 hours

    1 hour

    12 hours

    Idle

    None

    5 minutes

    Absolute session timeout

    For MongoDB Atlas for Government, limits include:

    Session Timeout
    Default
    Minimum
    Maximum

    Absolute

    12 hours

    1 hour

    12 hours

    Idle

    10 minutes

    5 minutes

    10 minutes

  3. Click Save.

    The settings apply to the user's next log in.

Specify a designated Atlas security contact to receive security-related notifications.

  • You can specify only one email address to receive security-related notifications including those from the MongoDB Security Team.

  • We recommend that you create a mailing list that uses a single address, and specify it as the security contact as a best practice. A mailing list can also send these notifications to multiple users.

  • Specifying a security contact does not grant them authorization or access to Atlas for security decisions or approvals.

  • If the account for the security contact gets deleted, the security contact setting is cleared, and the former security contact is shown as the modifier on the related notifications and events.

1

WARNING: Navigation Improvements In Progress

We're currently rolling out a new and improved navigation experience. If the following steps don't match your view in the Atlas UI, see the preview documentation.

  1. If it's not already displayed, select your desired organization from the Organizations menu in the navigation bar.

  2. Click the Organization Settings icon next to the Organizations menu.

    The Organization Settings page displays.

2
  1. In the Atlas Security Contact Information section, click .

  2. Specify an email address.

    Specifying a valid email address enables the Save button.

  3. Click Save.

To delete the currently specified security contact:

1

WARNING: Navigation Improvements In Progress

We're currently rolling out a new and improved navigation experience. If the following steps don't match your view in the Atlas UI, see the preview documentation.

  1. If it's not already displayed, select your desired organization from the Organizations menu in the navigation bar.

  2. Click the Organization Settings icon next to the Organizations menu.

    The Organization Settings page displays.

2
  1. In the Atlas Security Contact Information section, click .

  2. Delete the existing email address.

  3. Click Save.

Generative AI features are enabled by default in Atlas. When this setting is turned on, Project Owners can enable or disable individual AI features at the project level. To learn more, see Generative AI FAQs.

To disable generative AI features for all projects in your organization:

1

WARNING: Navigation Improvements In Progress

We're currently rolling out a new and improved navigation experience. If the following steps don't match your view in the Atlas UI, see the preview documentation.

  1. If it's not already displayed, select your desired organization from the Organizations menu in the navigation bar.

  2. Click the Organization Settings icon next to the Organizations menu.

    The Organization Settings page displays.

2

This disables Atlas features that use generative AI across all projects in the organization.

You can configure Atlas for the following integrations:

1

WARNING: Navigation Improvements In Progress

We're currently rolling out a new and improved navigation experience. If the following steps don't match your view in the Atlas UI, see the preview documentation.

  1. If it's not already displayed, select your desired organization from the Organizations menu in the navigation bar.

  2. Click the Organization Settings icon next to the Organizations menu.

    The Organization Settings page displays.

2

Click Integrations in the sidebar.

The Organization Integrations page displays.

3
4
  1. Type your workspace name into the field.

  2. Click Continue.

  3. Select your authentication method.

  4. Click Authorize.

5

Important

You can authorize only one Slack Workspace for each Organization.

1

WARNING: Navigation Improvements In Progress

We're currently rolling out a new and improved navigation experience. If the following steps don't match your view in the Atlas UI, see the preview documentation.

  1. If it's not already displayed, select your desired organization from the Organizations menu in the navigation bar.

  2. Click the Organization Settings icon next to the Organizations menu.

    The Organization Settings page displays.

2

Click Integrations in the sidebar.

The Organization Integrations page displays.

3

Important

This does not stop Atlas from sending alerts. To stop Atlas from sending alerts to Slack, you must delete the Slack alert setting.

You can connect your Atlas clusters to applications that you deploy using Vercel. To learn more, see Integrate with Vercel.

Back

Activity Feed

On this page