Skip to main content

Organizations

Organizations let a group own repositories, manage membership, and delegate access through teams.

Organization Model

  • Organizations own repositories, just like users do
  • Organization membership roles are owner and member
  • Teams are groups of users within an org with repository permission levels of read, write, or admin
  • Organization visibility controls who can see the org: public (visible to everyone), limited (visible to authenticated users), or private (visible only to members)

Managing Organizations

See the CLI reference for the complete list of flags and options.

Members

Organization members have either owner or member roles.

Teams

Teams provide granular access control within an organization. Each team has:
  • A name and description
  • A team permission level (read, write, or admin)
  • A set of repositories it has access to
  • A set of member users

Creating and Managing Teams

Managing Team Members

Managing Team Repository Access

Roles and Permissions

Our permissions systems are generally not stable and are liable to have breaking changes as we find the correct abstraction for permissioning agentic workflows.
Organization membership roles Team permission levels

Repository Ownership

Repositories can be owned by either a user or an organization:
The --org flag for jjhub repo create posts to /api/orgs/:org/repos instead of /api/user/repos. If --org is not yet available in the shipped CLI, use the API fallback: jjhub api -X POST /orgs/my-org/repos -f name=new-project -f description="Org repository".
Org-owned repos inherit team-based access control. Direct collaborator access is also supported for individual users.