Docs Menu
Docs Home
/
Cloud Manager
/
Organizations & Projects

Manage Organizations

An organization can contain multiple projects. Under this hierarchy structure, you can:

  • Use the same billing settings across all projects in your organization.

  • Use the same alert settings across all projects in your organization.

  • View all projects within an organization.

  • Bulk assign users to projects with teams.

Create an Organization

Note

When you create an organization, you are added as an Organization Owner for the organization.

1

View all of your organizations.

  1. Expand the Organizations menu in the navigation bar.

  2. Click View All Organizations.

2

Click New Organization.

3

Name your organization.

  1. Provide a name for your Organization.

  2. Select Cloud Manager.

You have the option of adding a new Cloud Manager organization or a new MongoDB Atlas organization. To learn more about MongoDB Atlas, see MongoDB Cloud Services.

4

Add members to your organization.

  1. For existing Cloud Manager users, enter their username. Usually, this is the email the person used to register.

  2. For new Cloud Manager users, enter their email address to send an invitation.

5

Specify the access you want to grant the organization members.

6

(Optional) Disable the IP access list requirement for the Cloud Manager Administration API.

When you create a new organization, Cloud Manager requires IP access lists for the Cloud Manager Administration API by default. If you require an IP access list, your Cloud Manager Administration API keys can make API requests only from the location-based IP or CIDR addresses that you specify in the IP access list.

To disable the IP access list requirement and allow your Cloud Manager Administration API keys to make requests from any address on the internet, toggle Require IP Access List for the Cloud Manager Administration API to OFF.

To learn more, see (Optional) Require an API Access List for Your Organization.

7

Click the Create Organization button create the organization.

Once you create the organization, you can add projects, users, and set the billing information for all projects within the organization.

Configure Session Timeouts

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 Cloud Manager UI without re-authenticating. The idle session timeout specifies the maximum duration a user can remain inactive before Cloud Manager 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.

Considerations

  • 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, Cloud Manager displays a message allowing the user to continue the session.

  • Timeout configurations apply only to the Cloud Manager 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 Cloud Manager credentials. A fixed 12-hour session timeout applies instead of the custom values.

    • sessions where users log in through 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 Cloud Manager web session ends.

Procedure

1

Navigate to the Organization Settings page.

In MongoDB Cloud Manager, go to the Organization Settings page.

  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

Set the absolute and idle session timeouts.

  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 Cloud Manager, limits include:

    Session Timeout
    Default
    Minimum
    Maximum

    Absolute

    12 hours

    1 hour

    12 hours

    Idle

    None

    5 minutes

    Absolute session timeout

  3. Click Save.

Leave an Organization

Important

You can't leave an organization if you are the last Organization Owner for that organization.

1

View all of your organizations.

  1. Expand the Organizations menu in the navigation bar.

  2. Click View All Organizations.

2

Leave the organization.

For the organization you wish to leave, click its Leave button to open the Leave Organization modal.

3

Click Leave Organization to confirm.

Delete an Organization

Important

To delete an organization, you must have Organization Owner role for the organization.

You cannot delete an organization that has active projects. You must delete the organization's projects before you can delete the organization.

1

In MongoDB Cloud Manager, go to the Organization Settings page.

  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

Delete the organization.

  1. If it is not already displayed, click the General Settings tab.

  2. Click Delete.

    This displays the Delete Organization dialog.

  3. Click Delete Organization to confirm

Back

Organizations & Projects

Next

Connect to Atlas

On this page