Organizations, membership, and ownership

Every repository and API token has one owner. Joining an organization gives you access to its resources without changing your personal repositories or tokens.

Owner	Best suited for	Who manages it
Personal account	Personal projects, experiments, and packages maintained by one person	The account owner
Organization	Shared packages, team projects, and CI that should outlive one member	Organization administrators

Create an organization

Open Organizations, create one, and invite members by email. The creator becomes an administrator.

Tip

Select the intended owner before creating a repository or token. A personal-account PAT cannot access organization repositories. An organization-account PAT targets one organization and remains limited by its owner’s current membership access.

Administration

Administrators manage organization settings, repositories, tokens, invitations, members, and administrator roles. Ravenstash prevents removal of the final administrator.

Choose the right owner

Use an organization when packages or CI credentials should outlive one member. Otherwise, personal ownership is appropriate.

Namespace access is required for repository access. Administrators can further restrict a repository to selected members with Read or Publish access, or to administrators only. Private mirrors have their own member access.

Organization automation tokens use explicitly selected resources and permissions. Create a separate token for each CI or release workflow and revoke it when that workflow no longer needs access.