Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
76 results found
-
More granular user privileges for Database User in same project
When having several clusters in the same project, it would be nice if we could configure different privileges to different clusters for the same user credentials.
Like in the following example
Name | Cluster1 | Cluster2 | Cluster3 | Cluster4
User1 | R/W | R | R | R/W
User2 | R | R/W | R | RCurrently it's not possible to specify different privileges on the cluster level.
11 votes -
Manage Database Access and Network access
I would like to give colleagues the ability to manage Database Access and Network access for a project without giving the the project owner role.
A way to provide more granular access in Atlas would be nice
11 votes -
Show last activity of user
For managing Database Users, it would be nice to see when that user was last used to authenticate with the cluster - so that we can spot potentially unused accounts and to act as an extra layer of confirmation when deleting accounts that we think are not needed anymore.
10 votes -
Ability to invalidate or revoke a X.509 certificate that was not expired.
Currently, X.509 certificates can be issued for authentication and authorization. However, it is not possible to invalidate an already issued certificate. In a situation where the certificate would be compromised, it is therefore not possible to invalidate it and re-issue a new one. The only way is to delete the user associated with the certificate and create a new user account (New CN).
10 votes -
Ability to enable LDAP and IAM auth at the same time
We would like the ability to have LDAP and IAM auth enabled on the same cluster at the same time. Today, you can only have one enabled, not both. Our goal is to use IAM auth for programatic access and LDAP auth for human access.
Please let us know when this gets prioritized.
9 votes -
Atlas User permissions/role by Cluster
It would be very helpful to restrict/allow access to clusters within an Atlas project, by Atlas user. This can be achieved with database users, but Atlas users have all or nothing access to the clusters within a project.
9 votes -
Ability to change First and Last Name
It would be good if users are able to modify their First and Last Name after account creation.
8 votes -
Identify users via API that are regular project users versus federated or built-in (e.g., charts) users
Expand the API to allow a way to identify and differentiate federated users and other non-manageable users (like "Charts User") from regular project users in MongoDB Atlas using API output, similar to how the Atlas UI visually marks federated users. For example, the Atlas UI displays a greyed-out edit icon and the ScreenTip displays a "Roles are managed through federated role mapping".
7 votes -
A new role for security auditing purposes
Currently MongoDB Atlas provides two read only roles at project level ("Project Read Only", and " Project Data Access Read Only").
"Project Data Access Read Only" seems to allow access to the data also, while "Project Read Only" role does not allow access to the logs. (https://www.mongodb.com/docs/atlas/reference/user-roles/)
For security officers (internal/external), they need to access to the logs (audit, access, etc) and also to review the configuration; but don't need access to the data.
Therefore, I would like to request a new project level role for security officers with following features.
- access to "Download Logs"
- access…7 votes -
Associate domains to an IDP at Organization level rather than for entire mongodb.com
At this time domain to IDP associations apply to entire mongodb.com. This makes it very difficult for large companies that have several independent departments to use mongodb.com. Some departments might want to create separate Atlas organizations and others simply access Support section of mongodb.com web-site. They wouldn't want to share an IDP created within one Atlas organization.
One possible approach to addressing this issue is for an Atlas organization to have a distinct sub-domain on mongodb.com (e.g. bigco-org-a.mongodb.com). Another approach would be to have a field for Atlas Organization name on logon page.
7 votes -
make empty teams possible
It is currently not possible to create empty teams of remove all users from teams.
We would like to arrange our access management through teams. For our production environment we want a 'read only' and an 'admin' team. The admin team should be empty at all times, except in the case of incidents where we want to add specific users to the admin team to be able to solve the incident.7 votes -
Day granularity for Atlas-managed X.509 certificate
It would be great to add more granularity when creating an Atlas-managed X.509 certificate for a MongoDB user, i mean by day at least.
Thank you7 votes -
Support OIDC as Authentication Protocol for access to Mongo Portal
Currently SAML is supported: https://www.mongodb.com/docs/atlas/security/federated-authentication/#configure-federated-authentication
It would be preferable if OIDC was supported.
6 votes -
Atlas access management similar to Azure AD Privileged Identity Management (PMI)
Hello, we are looking for functionality that allows users to auto-promote or adjust their privileges based on the access needed.
For example: if user XYZ needs access to DB:123 he can elevate access himself to this db.
This would be similar to Azure Active Directory (Azure AD) Privileged Identity Management (PIM). A service offered by Microsoft as part of its Azure cloud platform. It helps organizations manage, control, and monitor access within their Azure AD environment, particularly for privileged accounts. These accounts have elevated permissions that can perform critical tasks, such as managing resources, configuring settings, or accessing sensitive data.
…
6 votes -
Reuse email address for new Atlas account
Please allow email addresses to be reused/reinstated for new Atlas accounts if an Atlas account associated with that email address has been deleted.
6 votes -
My entire team receives the billing info every month.
Billing should be limited to organization owners only and not viewable by the entire organization.
6 votes -
Project Monitoring Admin -- Access
Hi Team,
We need to give access to a particular team so they can create, edit, clone, disable, and delete the alarm for the entire organization in Alert setting only.
We should not give them access other than the Alert setting. Is there any way to give access for Alert setting only, kindly provide your suggestions at the earliest.
Please provide us steps if there's any way to create custom access for alert settings alone.
6 votes -
Change Username
Ability to change your username after registration and be able to re-use it should you need to.
6 votes -
Return a user createdDate for Atlas control plane and database users
Automated user systems such as Hashi-Vault will automatically create users. Typically these users have a 90day expiration. Any team using continuous delivery hits the atlas user limit. There is not a way to know when an atlas user was created from the API data
5 votes -
Add support for custom comment field per API key access list entry
Currently, in the API Access List for an API Key in MongoDB Atlas, there is no way to associate metadata or context with each IP address or CIDR block. This makes it difficult to track the purpose or ownership of each entry, especially in environments with multiple users, services, or automation systems.
Please add support for an optional comment (description) field for each entry in the API Access List associated with an API Key. This field would allow users to provide human-readable context, such as:
- Who owns this IP address or range
- What system or service it corresponds…4 votes
- Don't see your idea?