Atlas

Share your idea. In order to help prioritize, please include the following information

  1. A brief description of what you are looking to do
  2. How you think this will help
  3. Why this matters to you

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Allow access from anywhere button to be a separate UI permission

    "allow access from anywhere" button should be a separate privilege. This would allow the ability to add it to a role. The goal is to allow developers to log into the control plane, use the UI to add 1 single IP(theirs)...but not open up IPs to all(0.0.0.0/0).

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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 | R

    Currently it's not possible to specify different privileges on the cluster level.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  3. Granular Permissions

    Right now Mongo Atlas allows you to assign two types of roles to all the users: Organization and Project, and for each set it gives you some predefined roles.

    The problem with this is you can't have any kind of granular control of what permission is assigned to each user. (e.g. to allow a user to create a trigger through Mongo Stitch it needs the Project Owner role).

    This is a major setback as I'm giving my coworkers more access than needed.

    A good solution would be to have something like the database access control in this part so we…

    228 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  25 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  4. Support GCP IAM for Cluster Authentication

    Achieve feature parity with AWS IAM cluster authentication support.

    51 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  5. RBAC for Atlas Search

    Atlas Search Indexes can only be managed via MongoDB credentials (Terraform or API calls), with required role "Project Data Access Admin" (see https://docs.atlas.mongodb.com/reference/api/fts-indexes-create-one/#required-roles ). It would be great if we could create/delete search indexes using database credentials, similarly to regular indexes.

    Because of that constraint, we need to provision dedicated apikey for our application ; in order to create the relevant search indexes. However, providing "Project Data Access Admin" is too much of a security risk - considering the power of such role.

    Would it be possible to have dedicated "Atlas Search Admin" role which would allow creation / updating…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  6. More Fine-Grained Custom Roles

    Our developers need to access databases from home or an office location from time to time.
    They are not Project Owners and should not have broad sweeping administrative privileges over the databases.
    In some cases they may be outsource workers who would only have read-only views on the data.
    However, they do need to be able to connect to the databases.
    Currently, you need a Project Owner role to be able to add an IP address to the whitelist and allow remote access.
    Please add the ability to create custom roles for Atlas users, which would enable us to create…

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  7. Allow modifying federation role mappings via API

    We would like to use the new role mapping feature for federated authentication to assign Atlas roles based on LDAP groups assigned to our users.

    However, we frequently create new projects programmatically and would need to manage the permissions to these new projects using role mapping. However, there is no public API available to manage role mappings programmatically. In addition, enabling role mapping disables the ability to manage roles for federated users with the API. So, at present, role mappings and permissions can only be managed manually through the UI.

    We would like to request the ability to modify role…

    23 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  1 comment  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  8. Allow custom duration for Temporary Users

    In our software development lifecycle, we have sprints that are 2 weeks long.

    We create temporary users for Software Engineers that are "onCall" during a sprint. The role is moving to a different engineer each new sprint.

    It would be great to be able to specify an explicit deleteAfterDate value or a custom duration greater than the current 6 days.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  9. Support Login with Microsoft Credentials

    When login to Atlas, we can use Google Login at the moment.
    Please add Login with Microsoft Credentials.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  10. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  12. Being able to enable / disable Database users

    When managing accounts and permissions, it could be great to "disable" an account before deleting it or reseting its password.

    By example GCP ServiceAccounts have this feature. It helps to restore a service of an account faster if this one is still in use.

    It will also help to set a kind of "policy" where inactive accounts get deactivated for a period of time and then deleted if not reactivated till then.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  13. Project teams

    Hello,

    I think it would be a good idea to have team management at project level.
    We have many projects and members in our Atlas account.
    I'm a organization owner. The people in my organization use the Altas service. I create
    a project for them and give my colleagues the project owner authorizations.

    Project owners can invite other members. This is good. But it's a little inconsistent that
    they are not able to create groups or teams within their projects They have to manage the permissions for each member separately.

    We can't use organization teams, because they are located at…

    32 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  14. Improve password manager support on login screen

    Currently on the Atlas login screen it presents a button to authenticate using Google and a text field to enter an email address. Upon entering an email address there's a brief pause - presumably to check if the email address is bound to a configured SAML provider - and if not then the password field appears.

    Since the password field doesn't exist in the DOM until it's needed it means password managers have to autofill the email and password fields as two separate steps. I propose to have the password field present and hidden from the start so that password…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow an "Any Database" option for actions in custom roles

    Much like built-in roles have the ability to target all databases/any database, it would be ideal if collection actions could also target any database. Similarly to how, when adding collection actions to a custom role, if you leave the "collection" field blank, it applies to all collections in the specified DB, it would be great if you could leave the "database" field blank too (or add an "any database" option) and have the actions associated with the role be allowed on any database.

    This feature gap creates unnecessary maintenance overhead for clusters with large numbers of databases. This is particularly…

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  17. more information in AWS IAM audit logs

    We are using MongoDB-AWS for authentication, and have set up the audit log to log events taken by AWS roles. However, there is insufficient information in the logs to identify who is doing those actions, as roles can be assumed by multiple people.

    An example log line in the current audit log:
    { "atype" : "authenticate", "ts" : { "$date" : "2021-01-05T00:21:52.628+00:00" }, "local" : { "ip" : "192.168.248.203", "port" : 27017 }, "remote" : { "ip" : "172.31.0.5", "port" : 54195 }, "users" : [ { "user" : "arn:aws:sts::555555555555:assumed-role/developer-role/", "db" : "$external" } ], "roles" : [ {

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  18. Authentification on Azure (IAM)

    Hello,

    We absolutely need a more modern authentication method than using LDAPS to authenticate users against the MongoDB databases that we deploy with Atlas. When will we see a modern authentication service at this level? Ideally, we want cloud functionality equivalent to AWS IAM but on Azure.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  19. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  20. Support for User Groups with Separate Authentication Configurations

    Currently Atlas only uses a single (flat) user group which only allows for 1 type of authentication per Organization.

    However if Federated Authentication is enabled, the authentication mechanism in Atlas is bypassed for the IdP based on the domain name of the user and the configuration of Atlas Authentication.

    This causes a problem if there are multiple groups of users who all share a domain name, some of whom are registered in an IdP, and some of whom are not registered in an IdP (for example users in 2 divisions of the same company).

    In this scenario, users who are…

    19 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base