Hello,

I would like to add to this feature request:

The current role concept works fine as long as one of the predefined roles aligns with your specific needs. However, if this is not the case (for example, when some automated actions need to be performed at the organizational level) the only available option is to create an API key and fall back to the Organization Owner role. (Service Account credentials would also work, but the issue stays the same.)

The concern with this approach is that the Organization Owner role has an excessively broad scope. A token with this level of access effectively grants unrestricted control over the entire organization. While measures can be taken to safeguard such a token, any potential leakage would pose a significant security risk and could have severe consequences.

A compromised token with Organization Owner privileges represents a critical threat to data protection. The extensive scope of this role increases the potential blast radius, which could result in substantial financial and reputational damage—not only for us as a customer, but also for MongoDB as the service provider.

At present, there appears to be no viable alternative, leaving us reliant on the Organization Owner role.

This limitation is not in line with the expectations for an enterprise-ready service offering. Compared to other SaaS providers, more granular and least-privilege access controls are typically available and strongly recommended.

I believe that security features should be considered a top priority.

The current permissions management only offers a few roles at the organizational and project levels, and in some cases requires assigning a role with more permissions than desired.

I believe this feature should be taken into consideration for short-term implementation.

We have been waiting for this feature for at least five years.

It is essential to streamline and strengthen our internal and external audit processes. As it stands, the lack of enterprise‑grade capabilities in this area forces us to rely on costly, complex workarounds that are difficult to audit and maintain.

We urge you to evolve the platform to deliver functionality that is aligned with the real requirements of large organizations, particularly in terms of governance, traceability, and compliance.

we have a need to allow certain users to be able to view the size of collections without being able to read the collection data.

the only roles I can use today that allows viewing of collection sizes is Project Data Access Read Only. But this also allows reading of collection data, which we don't want to allow.