Skip to main content
Your account lives in one organization — the billing and membership boundary. Credits are pooled across it, and everyone you invite shares it. Projects belong to the org, but access to each one is granted per project, not org-wide.

Members and roles

An org owner or admin invites people by email; accepting the invite adds them to the org. Every member holds one role:
RoleCan
OwnerEverything — edit org settings and billing, invite or remove members (any role), change roles.
AdminInvite members (member or admin) and revoke invites.
MemberBelong to the org and to the projects they’re added to.
Where: Platform → ProfileOrganization — invite and manage org members.

Projects aren’t shared by default

Adding someone to the org does not hand them your projects. Each project is private to the people explicitly added to it — so teammates in the same org can work on entirely different projects without seeing each other’s. To grant access to a specific project, its owner invites the person from Project Settings → Members — by email, or one-click for existing org members during the project wizard. Project roles are owner and member. This keeps work compartmentalized: bring a contractor or teammate into just the one project they need, without exposing the rest of the org’s. For work whose context must not even reach shared org memory, see memory-isolated projects.

See also