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?

UI update that lets you know the reason you can't add user/pass auth until initial realm sync is deployed.

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

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.

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

In RealmSwift, one can define LinkingObjects to refer to inverse M2O or M2M relationships. These are not supported by queries in MongoDB requiring to create custom resolvers. It would be very useful if these would be accessible in GraphQL.

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.

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

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.

It would be useful to have an integrated GraphQL client that is authenticated against the cluster available in Realm functions, to create stored queries and modify these in postprocessing in a Realm function.

Currently, You need to be a "Project Owner" to view GraphQL configurations in Realm Web. I also need "Project Owner" to execute a schema validation. I would like to see more granular access controls for Realm Web similar to the granularity of MongoDB Atlas.

In my application I have implemented a custom confirm function which blocks registrations unless they have an email address in my company's domain. When this is the case, I would like to send the signup email as usual. However there isn't a way of doing this so in order to implement this basic filter I have to setup a 3rd party email service.

It would be good to allow calling the default confirmFn from within the custom one

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.

We have Realm applications running in Dev, Staging, Production.
Someone accidentally deleted the Staging application. (It's easy to do it)
Hopefully, it wasn't a production one.
Please add a way to lock or prevent Application and Cluster deletion.
That way, we add an additional step which is a password, for example, and prevent accidents to happen.
Thanks!

Right now there is Google, Facebook, and Apple as auth providers. Would like to see Github added as well.

When creating a free cluster to evaluate realm-ui and sync please warn that 4.4 or higher mongo is required.
Now i found out when getting started that i have a cluster with 4.2.1 and cannot use the task tracker app sync.

We need a way for ids to not have to be unwrapped from $oid before they are assigned as an ObjectId.

Incoming data:

{"_id":{"$oid":"..."}}

Realm class:

class Item: Object {
@objc dynamic var _id = ObjectId.generate()
}

That's all that should be needed.

So the default ObjectId class needs:

enum CodingKeys: String, CodingKey {
case oid = "$oid"
}

then in init(from decoder:Decoder)

let container = try decoder.container(keyedBy: CodingKeys.self)
try super.init(string: try container.decode(String.self, forKey: .oid))

Do that when the .singleValueContainer() call fails.
That way both use cases are satisfied.