128 results found

1. Backup Encryption Visibility in MongoDB Atlas UI (Default Encryption)

   Hello,

   I would like to propose an enhancement to the MongoDB Atlas user interface to improve visibility of backup encryption status, specifically when using Atlas's default encryption (i.e., without a customer-managed Key Management Service - KMS).

   Currently, the Atlas UI displays encryption details only when a customer-managed KMS is configured (e.g., via Snapshot Details > Encryption Key ID). However, when relying on Atlas's default encryption, there is no visible confirmation in the UI that backups are encrypted.

   From an audit and compliance standpoint, the lack of visible encryption status in the UI when no customer-managed KMS is configured often leads to confusion. Specifically, the UI displays “Encryption Key ID: Not enabled”, which can be misinterpreted by auditors as meaning that encryption itself is not enabled, even though Atlas applies encryption by default.

   This discrepancy forces teams to spend time explaining and justifying something that could be clearly and transparently shown in the interface. If encryption is always enabled by default, it would make a lot of sense to reflect that directly in the UI. A simple note like “Encrypted using default provider-managed keys” would go a long way in reducing friction and improving trust during audits.

   Suggested Enhancement:
   Add a visible label or confirmation in the Atlas UI (e.g., within Snapshot Details or Backup Settings) indicating that backups are encrypted when default encryption is in use.

   We believe this small but impactful change would greatly improve transparency and support audit readiness for many users working under strict compliance requirements.

   Please let us know if further clarification is needed. We appreciate your consideration.

   Best regards,
   Diego Gava Monteiro
   Analyst, Database Engineering – Espírito Santo, Brazil
   Pismo

   Hello,

   I would like to propose an enhancement to the MongoDB Atlas user interface to improve visibility of backup encryption status, specifically when using Atlas's default encryption (i.e., without a customer-managed Key Management Service - KMS).

   Currently, the Atlas UI displays encryption details only when a customer-managed KMS is configured (e.g., via Snapshot Details > Encryption Key ID). However, when relying on Atlas's default encryption, there is no visible confirmation in the UI that backups are encrypted.

   From an audit and compliance standpoint, the lack of visible encryption status in the UI when no customer-managed KMS is configured often leads… more

   •  

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Atlas  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Display of Default Backup Encryption in MongoDB Atlas UI

   Hello,

   I would like to propose an enhancement to the MongoDB Atlas user interface to improve visibility of backup encryption status, specifically when using Atlas's default encryption (i.e., without a customer-managed Key Management Service - KMS).

   Currently, the Atlas UI displays encryption details only when a customer-managed KMS is configured (e.g., via Snapshot Details > Encryption Key ID). However, when relying on Atlas's default encryption, there is no visible confirmation in the UI that backups are encrypted.

   For compliance and audit purposes, it is critical to have a clear and explicit indicator in the Atlas interface confirming that backups are encrypted—even when using the default encryption provided by Atlas. This would help teams meet regulatory requirements and demonstrate data protection measures without needing external configurations.

   Suggested Enhancement:
   Add a visible label or confirmation in the Atlas UI (e.g., within Snapshot Details or Backup Settings) indicating that backups are encrypted when default encryption is in use.

   We believe this small but impactful change would greatly improve transparency and support audit readiness for many users.

   Please let us know if further clarification is needed. We appreciate your consideration.

   Best regards,
   Diego Gava Monteiro
   Analyst, Database Engineering – Espírito Santo - Brazil

   Hello,

   I would like to propose an enhancement to the MongoDB Atlas user interface to improve visibility of backup encryption status, specifically when using Atlas's default encryption (i.e., without a customer-managed Key Management Service - KMS).

   Currently, the Atlas UI displays encryption details only when a customer-managed KMS is configured (e.g., via Snapshot Details > Encryption Key ID). However, when relying on Atlas's default encryption, there is no visible confirmation in the UI that backups are encrypted.

   For compliance and audit purposes, it is critical to have a clear and explicit indicator in the Atlas interface confirming that backups are… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Atlas  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Scrap data explorer preview. It's extremly slow and not usable. I would like to go back to the predecessor of the data explorer.

   Scrap data explorer preview. It's extremely slow and practically not usable. I would like to go back to the predecessor of the data explorer. The problem is by mistake if you selected it you can't turn it off. So now I'm unable to access production data completely. It's just early days kill this feature and save further development cost.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Atlas  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Profiler filters

   It would be nice to be able to filter the content of the profiler in the Atlas GUI.
   The profiler has proved to be very useful and maybe it could be even better.

   Currently you can only filter by "Top namespace operations"; and it would be nice to also filter by:
   - readConcern: this is because the ones hitting a secondary node are usually not a concern to me. They tend to be ad hoc queries which do not always have a supporting index and that is ok.
   - Also, when Operation = command, it could actually be many things. It might be a simple FIND or an AGGREGATE or even an INSERT. So filtering by the type of Operation would be good.

   It would be nice to be able to filter the content of the profiler in the Atlas GUI.
   The profiler has proved to be very useful and maybe it could be even better.

   Currently you can only filter by "Top namespace operations"; and it would be nice to also filter by:
   - readConcern: this is because the ones hitting a secondary node are usually not a concern to me. They tend to be ad hoc queries which do not always have a supporting index and that is ok.
   - Also, when Operation = command, it could actually be many things.… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Others  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Support ISODate() when inserting a document via UI

   When inserting a JSON document via the UI (browse collections), it would be great if using ISODate() would be allowed. Currently one has to resort to {"$date":{"$numberLong":"1748952000000"}}, which is quite a bit counterproductive for manual edits/inserts.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Bulk‐delete documents directly from the Atlas Collections UI

   Right now, Atlas only lets you delete an entire collection or run a “drop” command—you can’t remove individual documents (or a selection of documents) from the web UI. It would be extremely useful to add:

   A Delete action next to each document in the Find view
   
   A checkbox column so you can select multiple documents
   
   A “Delete Selected” button that prompts for confirmation
   

   This would let developers and DBAs quickly remove test data, expired records, or bad imports without switching to Compass, writing a manual query, or dropping and recreating collections. It would improve productivity and reduce the risk of accidentally dropping an entire collection just to purge a few documents.

   Right now, Atlas only lets you delete an entire collection or run a “drop” command—you can’t remove individual documents (or a selection of documents) from the web UI. It would be extremely useful to add:

   A Delete action next to each document in the Find view
   
   A checkbox column so you can select multiple documents
   
   A “Delete Selected” button that prompts for confirmation
   

   This would let developers and DBAs quickly remove test data, expired records, or bad imports without switching to Compass, writing a manual query, or dropping and recreating collections. It would improve productivity and reduce the risk of… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Atlas  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Quick Go To Reference

   I've only been using Compass for literally 2 hours, and am not an experienced DB admin at all, but have searched in vain to try and see if I'm missing something.

   My documents have lots of fields that are references to other documents, so contain ObjectId's. I'd love a quick way to jump to a referenced document via it's ObjectId.

   Maybe there are good technical reasons this couldn't work, but would love to be able to right-click an ObjectId and "Go to document".

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  General Navigation  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Aggregation Number of Docs To Preview Does Not Work Above 20

   The Atlas UI Aggregation Setting "Number of Preview Documents" allows you to set values greater than 20, and then just ignores the set value and still returns 20.

   See this support case for additional details: https://support.mongodb.com/case/01426836

   The documentation does state that the maximum preview docs is 20. However, the UI should not happily except values greater than 20 and ignore the setting.

   •  

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Atlas  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Org Owners should see all projects that a user belongs to in the UI or in CLI

   Should be possible to see all projects that a user belongs to, in the UI or in the CLI, instead of having to go into all existing projects to see if this user is there or not

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Atlas  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Default Org creation

    Don't create a "me" Org by default the first time I login. I'm not creating anything independent, so I don't need my own Org. I need to use the Org owned by the domain my email address belongs to.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  MongoDB Account  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. UI is cluttered, wireframe-like, and does not orient user attention appropriately

    There is simply too much going on on screen that is given the exact same visual weight.

    You need to use more colors in the color scheme, use icons that are more individually unique. You also need to define some different regions using more noticeable background colors. Serif fonts also introduce a complication in designing for articulate use of space, because it conflicts with block design.

    All in all, the website design does not help orient user attention to the overall mental model of the features: the features are not prioritized and nested very well. You need to reduce how many unrelated details are showing at the same time. Some of the tips above will help contextualize details to let the user separate their thoughts, but reducing details can also help.

    Loosely speaking, you need to arrange your interface with bigger ideas to the left of smaller ideas, and bigger ideas above smaller ideas. As you can see in the attached screenshot, this is almost what you do, but you violate this principle by putting a large category "Data Services" to the right of the project name, separating it from its content underneath. That "Data Services" thing behaves like a tab. It should not be presented in a "breadcrumb"-like view next to the project name. It is not a file address or URL. Use conventional UI metaphors that work. Stop trying to follow the trends of disjointed UI arrangements. They only work when there is very little information on screen.

    There is simply too much going on on screen that is given the exact same visual weight.

    You need to use more colors in the color scheme, use icons that are more individually unique. You also need to define some different regions using more noticeable background colors. Serif fonts also introduce a complication in designing for articulate use of space, because it conflicts with block design.

    All in all, the website design does not help orient user attention to the overall mental model of the features: the features are not prioritized and nested very well. You need to reduce how… more

    •  

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  General Navigation  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Display group name and roles in "Organization Role Mappings"

    When using Azure EntraID to sync groups with Atlas Role, the page "Organization Role Mappings" only displays the GUID of the group. It would be nice add the following:

    1. Display the actual name of the group as defined on EntraID, so that Atlas users don't have to go to EntraID and search for the GUID to figure out what group is configured on Atlas.

    2. Display the roles already configured on a group, so that Atlas users don't have to click on the pen icon (edit) to access that information. Asking users to edit their configuration in order to read it is risky and could lead to unintended changes.

    Thank you

    When using Azure EntraID to sync groups with Atlas Role, the page "Organization Role Mappings" only displays the GUID of the group. It would be nice add the following:

    1. Display the actual name of the group as defined on EntraID, so that Atlas users don't have to go to EntraID and search for the GUID to figure out what group is configured on Atlas.

    2. Display the roles already configured on a group, so that Atlas users don't have to click on the pen icon (edit) to access that information. Asking users to edit their configuration in order to read it… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  IAM / SSO  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Allow to set first day of week

    Hi MongoDB,

    Please allow to select in user preferences first day of week. It is a pretty standard thing in internalization of products. We have Monday as first day of week and it is really cumbersome to pick right date when setting various date filters in Atlas UI.

    Thanks.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Titles while hovering

    When hovering buttons or other interactive UI Elements.. Have a small box to show up and tell it what it does. Like a the title attribute.

    This make the experience as a new member much smoother and for us that don´t log in that often.

    •  

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Others  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Reduce the height of ribbons

    In atlas we have multiple ribbons
    - Atlas (with your organizations)
    - Projects (with Data Services and Charts)
    - The cluster view (with the big ribbon containing all tabs, the path to cluster, the version, region)
    - The database view

    The two latest ribbons are so big, and reduce the view reserved to display the query results.

    It could be great to collapse the two ribbon as it is possible with Microsoft Office Suite

    •  

    •  

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Atlas  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Removal of unavailable metrics button from UI after cluster update based on cluster version.

    I updated cluster from V6.x.x to V7.x.x, and found that (Tickets Available) graph is showing available r/w tickets near 0. It was a little scary at a time but, after talking to support, I got to know (Tickets Available) is no longer supported but same info is available from (Queues) graph.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Atlas  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Sort collections by the column headers

    When you click into a database you see all the collections that are in it, their size, indexes, number of records, etc etc. It'd be awesome if those columns are clickable to sort the table. I'm trying to find the largest collections and collections with the most indexes and I'm having to scan through 100+ rows. Seems like low hanging fruit.

    •  

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Atlas  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Faster way to create cases in the Support Portal

    Faster way to create cases in the Support Portal

    9 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Others  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Hostname lookup/search capability in Ops Manager at global level

    This would give customers the capability

    • To tell which project a host belongs to do some sort of lookup in Ops Manager

    • Go to a central place, put in the hostname, and see what the project belongs to

    For example in the UI on the all clusters view, be able to do a global search for the host instead Mainly for the UI

    at the moment there are 10 tags per project, but sometimes project has more than 100 hosts

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  General Navigation  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Atlas Metrics Tab to display the timezone as part of the date fields

    Atlas Metrics Tab to display the timezone as part of the date fields

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating