Organizations & teams

Organizations

An organization is a shared space for:

• Repositories owned by the org (rather than a single personal account).
• Members with organization-level roles (admin, member, etc., as your deployment defines).
• Billing and usage limits tied to a subscription (when applicable).

Common flows

1. Create an organization — From the dashboard (if allowed by your plan).
2. Invite members — By email or user identifier; assign org roles.
3. Create repositories under the org — Slugs are unique per org.

Personal vs organization repositories

Some users have personal repositories (scoped to their user) and organization repositories. The create flow usually lets you pick the owner (org or self).

Teams

Teams group users so you can grant repository access to many people at once.

• Example: platform-team → Maintainer on core-skills repo.
• Users who join or leave the team see access updated accordingly.

If you don’t see Teams in your sidebar, your tenant may not use them or your role may not expose them.

Roles at different levels

• Organization role — What you can do across the org (invite users, manage billing, etc.).
• Repository role — What you can do in one repo (owner / maintainer / reader).
• Team membership — Can imply repository access without a direct user invite.

When in doubt, ask an organization owner or admin.