Atlas Organization Roles
Parent: MongoDB Atlas IAM and RBAC · Published reference · snapshot 2026-10-23 · skill mongodb-cohort-63131ca29156
↓ Facts as markdownall context files
Source-anchored research for Atlas Organization Roles. Run status: COMPLETED.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
Structure and components
- An October 18, 2026 user reported organization-access HTTP 403 after removing another member despite still seeing the Owner role. The thread contains no confirmed cause or resolution. (low confidence) (verified as of 2026-10-19) [source]
How it works
- Organization Owner inherits Project Owner on every project, even when assigned a weaker project role; inherited owners are absent from the project access list. (high confidence) (verified as of 2026-10-23) [source]
How-to and procedures
- Prefer narrower roles for routine integrations and reserve Organization Owner for operations requiring its broad authority. (high confidence) [source]
Problems, failure modes and limitations
- A user report describes an organization owner receiving an App Services access error that resolved itself after a couple of hours; support suspected a caching or browser-related issue. The report does not establish a general Atlas permissions defect. (low confidence) [source]
Facts and statements
- Organization roles govern organization-wide Atlas actions; owners manage user roles at that scope. (high confidence) [source]
- Organization Member can view organization settings and users but reaches only explicitly assigned projects. Organization Read Only can view settings, users, and all projects. (medium confidence) (verified as of 2026-10-14) [source]
- Organization Project Creator (ORG_GROUP_CREATOR) creates projects and inherits Member privileges. (low confidence) (verified as of 2026-10-14) [source]
- Organization Billing Viewer (ORG_BILLING_READ_ONLY) views billing and inherits Member privileges. Cloudaware requires Billing Viewer for read-only Atlas billing ingestion. (high confidence) (verified as of 2026-10-23) [source]
- Organization Billing Admin (ORG_BILLING_ADMIN) administers billing, manages billing alerts, and inherits Member privileges. (low confidence) (verified as of 2026-10-14) [source]
- Organization Stream Processing Admin (ORG_STREAM_PROCESSING_ADMIN) grants stream-processing ownership across projects, private-endpoint and VPC-peering management, and Organization Read Only privileges. (low confidence) (verified as of 2026-10-14) [source]
- SailPoint documents Organization Member plus Project Read Only for connector connection tests, Organization Owner for specified aggregation/provisioning operations, and Organization Read Only as an alternative for broad project visibility. (low confidence) (verified as of 2026-10-23) [source]
- Mondoo implements checks for at most three organization owners and no organization-owner API keys; these are its security-policy recommendations, not Atlas role-assignment limits. (low confidence) (verified as of 2026-10-23) [source]
- Organization Owner (ORG_OWNER) grants root organization authority, including settings, user administration, deletion, and all other organization-role privileges. (high confidence) (verified as of 2026-10-14) [source]
- Organization Member (ORG_MEMBER) can read organization settings and users, but sees only explicitly joined projects; project roles determine privileges there. (low confidence) (verified as of 2026-10-23) [source]
- Organization Read Only (ORG_READ_ONLY) provides read-only visibility across organization settings, users, and projects; SailPoint documents it as an alternative to per-project read-only assignments for specified discovery operations. (high confidence) (verified as of 2026-10-23) [source]
- SailPoint documents Organization Member plus Project Read Only for connection testing, and Organization Owner for entitlement changes. Treat these as connector requirements, not minimum permissions for every Atlas integration. (low confidence) (verified as of 2026-07-10) [source]
Children
- No children recorded.