Org owner should not be required for Atlas operations

[nirinchev]

Reporetd by Jesse Hall:

Tried to create an M0 cluster and it could not list available projects or create the cluster.

Could not connect to Atlas until enabling all available permissions for the Org service account.

Initially tried just Org project creator thinking that would include cluster creation, etc.

Ideally Org owner would not be needed as that is potentially too destructive to give to an AI.

[codeSTACKr]

• With Organization Read Only I can see all projects but not clusters or db's within

• With Organization Project Creator I can create new projects and clusters, db's etc within that project. But I cannot manipulate any existing projects, not even read.

• With Organization Owner I can do anything.

I tried combo's of Org Project Creator, Read Only, Member, but nothing allowed me to manipulate existing projects without Org Owner permission or Project level permissions.

If this is all as expected I think we just need to be very clear in our instructions/docs. It can be very confusing.