Skip to content

Atlas App Services

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

91 results found

  1. Configure rate limit

    It would be nice to be able to configure rate-limiting to prevent DDoS, scraping or unwanted requests that could highly increase the cost of MongoDB Realms

    58 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Ability to change/update email address of Application User

    Users should have the ability to change their email address.
    Applications cannot give the ability to users to change their own email address. Once a user is registered/created there is no way for such user to update/change their own email address.

    56 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Dark Mode

    Support a "Dark Mode" for the MongoDB Realm UI.

    40 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Export/import users in Realm app

    Option to export all Realm app users and import them.

    It's a major concern that users can't be exported. Both for backup reasons and also for moving them between apps.

    If you delete or loose a Realm app you are out of business because the users are gone and if you mistakenly chose the wrong deployment region, you can't move the app because you can't move the users.

    I think this is absolutely critical to growing a business using Realm apps.

    35 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. on premise solution

    Allow MongoDB to be used for on-premise solutions to offer early on integration or govcloud support for Realm.

    34 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Option to have Realm app users in an Atlas collection

    It would make a lot of sense to me if one could configure a Realm app to use a collection in the Atlas Cluster to store users instead of having a separate users database managed outside of Atlas, as the case is today.

    To avoid a breaking change, this could be implemented as an option to how users are managed today.

    This would solve most user-related feature requests and issues, as it would give the app developer full control of the user DB to do whatever queries or customization they want to. Maybe call the option "advanced" or such—more manual…

    31 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Need more close realm server in Asia

    currently realm server which can use in Asia is too far and limited like below link
    https://docs.mongodb.com/realm/admin/deployment-models-and-regions/#cloud-deployment-regions
    so, i think it has some delay to request realm server as well as management using realm web UI
    it would be nice to be able to use more close server

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    started  ·  Sumedha Mehta responded

    We have started work on more regions as well as cloud providers.

  8. Actual API Documentation

    There is various documentation for the many Realm/Stitch SDKs but almost no information about the underlying API endpoints, this needs to change and we need some detailed docs for working with the API itself.

    I am trying to get an app running with the GraphQL API but have found working with the authentication APIs to handle auth tokens and sessions to be a bit of a nightmare. This page https://docs.mongodb.com/realm/graphql/authenticate/ has some useful information but doesn't even give the endpoints for logging out or explain how to properly handle the email sign up process using API endpoints in place of…

    18 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. More Granular Realm UI Permissions

    At this time, the only permission that allows access to Realm is Project Owner; however, Project Owner grants permission to change a plethora of things inside Realm. In our case, we have testers who do not need the ability to change code. The testers only need to change Values and add users. Could a new permission class be created to support this?

    17 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Realm roles in Atlas Projects

    Currently we only have two roles available for Realm Users:
    1. Project Owner
    2. Project ReadOnly
    Would be great to have more roles for Realm Users with the ability to give access to specific Realm App or give access to Realm only without giving access to the entire project. Something like Realm WriteRead and Realm ReadOnly roles
    Thank you,
    Anton

    15 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. External Dependencies Management (npm)

    A lot of 3rd party libraries don't work, even ubiquitous ones like Joi. We upload zipped node_modules and all we get are errors.

    Devs now spend time building simplified versions of these libraries so we don't get the full benefit of a using a battle-tested library and also waste time writing functions that we shouldn't need to write. This is a huge pain and a productivity killer.

    15 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Terraform Provider

    It would be nice to be able to managed Realm Applications via Terraform, similar to how MongoDB Atlas can currently be managed via the mongodb_atlas from Terraform provider.

    13 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Add More Regions For Realm

    Would be great if we can have more options for realm like south america and europe.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Search Users by Email

    In the users tab, I can only search by ID. If I don't have the users ID, it's nearly impossible for me to find a user in the list. Need to be able to search for a user by email ASAP. Thanks.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. More descriptive errors

    We need more error codes for different situations. For example, using the wrong details while logging in returns 46 (Unknown), with a message indicating wrong credentials. In my app, 46 maps to a message like "An unknown error occurred. Please try again later.".

    It would be nice if wrong credentials had its own error type so I could send a more descriptive message.

    Please also consider this for any other error type that doesn't have a good reason for being Unknown.

    Thanks!

    10 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Customize Reset Password Email Link

    Users should be able to customize the reset password email that is sent to their users. This should include changing what the "sender" url looks like (noreply-stitch+mongodb.com => resetPassword@yourapp.com). Developers should have access to change look of the body of the email. This includes what is typed in the body, the title of the body and as well the company logo. I will upload a picture of how it currently looks and from my message understand what we want to change.

    8 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. More Intuitive GUI for Relationship Modeling

    I know "Add Relationship" button works very well. However, you can check some of Headless CMS out there and learn from how they are letting users to handle relationship modeling.

    I think the one from Strapi is the best. It's like attached image.
    You can search on google image by "Strapi relation" and find more images.

    8 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Atlas App Services regions in the UK

    UK Data Protection requirements often require data to reside within the UK, something that cannot be supported through Atlas App Services today.

    For all features (especially Charts, Realm and Triggers), being able to select the UK as a region would unlock additional customer use cases.

    Given I am a UK domiciled MongoDB Atlas user
    When I use MongoDB Charts
    Then all traffic should remain within the UK

    Given I am a UK domiciled MongoDB Atlas user
    When I use MongoDB Atlas Triggers
    Then I should have the option for my trigger to invoke from a UK data center

    Given I…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Allowed Request Origins should support URLs with wildcard characters

    The Allowed Request Origins list in the App Settings, at this time, doesn't support URLs with wildcard characters. As modern services like Vercel generate dynamically new URLs during development, the list needs to be updated every time with the current URL, while having an option available that would accept "https://*-myappname.vercel.app/" would simplify that step.

    5 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Increase RealmReturn Body Max Size

    The maximum return body size of a realm webhook is 4MiB (4194304 bytes). That might seem enough for most applications but when dealing with massive amounts of data, e.g. timeseries data over years, that is a hard limitation.
    It requires the client to make many more requests that would be necessary.

    In our special case we want to return one whole year worth of data per request to make things easier for our clients (currently they can get 3 months).

    Given a 16MB Limit on a MongoDB Collection Document, this would seem like a sensable option for a limit if…

    5 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    planned  ·  Drew responded

    Hi Marc – We have a ticket for this that’s near the top of the backlog and plan to increase the limit to 16MB in the near future.

← Previous 1 3 4 5
  • Don't see your idea?

Feedback and Knowledge Base