Organizations

Ownership boundary

Every project belongs to exactly one organization. The organization holds the team’s memberships, shared credit wallet, plan entitlements, provider installations, and domains. Spaces retain their own runtime and data isolation while consuming organization-level services.

Child organizations can represent workspaces or subaccounts. Billing resolves to the top-level organization, so sibling workspaces share the parent wallet without inheriting access to one another.

Administration

Organization settings are where administrators manage:

• members, invitations, built-in roles, and custom roles;
• spaces and the projects members may access;
• available credits, plan capacity, and auto-replenishment;
• installed Fork services and custom domains.

Access inheritance

Active administrators inherit down the trusted parent chain. Editors, Commenters, Viewers, and custom roles do not. A child administrator can manage that workspace and descendants, but receives no parent billing authority or sibling access.