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

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

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

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

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.

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?

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.

Add REST Services support analogous the GraphQL.
Some users on Realm desire a REST API to their clients as
oppose to a GraphQL API.

Although this can somewhat be accomplished by adding a HTTP '3rd Party Service' and query the mongo collections, you don't get all Rules, Schema, and other useful tools and services which are provided with the GraphQL option.

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

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.

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

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.

Please add a refresh button to the Logs view. I realize a browser refresh does the trick, but a button above the Logs table is more convenient.

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!

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.

Support client-side field-level encryption in MongoDB Realm.

https://docs.mongodb.com/manual/core/security-client-side-encryption/
https://docs.mongodb.com/manual/core/security-automatic-client-side-encryption/

Basically, it would be nice if we could mark fields as being "sensitive" in the schemas, and Realm Sync would make sure to encrypt the fields before they are sent from the client app to the MongoDB Atlas database.

In the documentation for anonymous auth, it says that Realm may delete anonymous users that are 90 days old https://docs.mongodb.com/realm/authentication/anonymous/

There is also a mention about 30 days of inactivity https://developer.mongodb.com/community/forums/t/persisting-anonymous-users/10247/2?u=anton_p

That's hard to rely on something so broad to make decisions in the app logic. Is it possible to clarify this behavior or provide control over this flow?