Right now Mongo Atlas allows you to assign two types of roles to all the users: Organization and Project, and for each set it gives you some predefined roles. The problem with this is you can't have any kind of granular control of what permission is assigned to each user. (e.g. to allow a user to create a trigger through Mongo Stitch it needs the Project Owner role). This is a major setback as I'm giving my coworkers more access than needed. A good solution would be to have something like the database access control in this part so we can create our own custom roles to assign to he users.

Update on March 12, 2026:

Thank you for all your feedback! I’m happy to announce that we have launched 15 new Atlas Project roles to provide more granular access control. You can find full details in our official announcement and documentation here: 15 New Purpose-Built Project Roles.

Since "granular permissions" is a broad topic and this thread covers many different product features, I am closing this feedback item to ensure we can track specific requests more effectively. Please vote/follow below feedback items instead. If you have new needs that has not been covered, please create a new feedback item. Thank you so much for making MongoDB Atlas better:

1. Custom Roles for Atlas Control Plane - https://feedback.mongodb.com/ideas/CUSTOMER-I-10525

2. Deny Assignments for Control Plane RBAC - https://mongodb.aha.io/ideas/CUSTOMER-I-10529

3. Attributed Based Authorization Support for Atlas Control Plane - https://feedback.mongodb.com/ideas/CUSTOMER-I-10526

4. Cluster Level Authorization https://feedback.mongodb.com/ideas/CUSTOMER-I-8520

5. Allow Granular Data access for Control Plane Users - https://feedback.mongodb.com/ideas/CUSTOMER-I-9848