Organization

An organization ties people, repositories, and org-wide controls together. Members still authenticate their own agents individually — see Agents & model access — and the organization is the shared layer on top.

What an organization owns#

• Members and roles. Owners, admins, and members, plus pending invitations. See Members & roles.
• GitHub App. The installation that gives the organization access to your repositories. See GitHub App.
• Agent authentication policy. Which managed authentication routes members may newly configure for their agents. See Agent authentication policy.
• Integrations. Which third-party tools are available to org-scoped agent sessions. Personal enrollment remains member-owned. See Integrations.
• Organization secrets. Env vars and files the settings UI makes available to every member's agent sessions.
• Billing. Seats, plan, and usage, managed from the Billing screen linked in Organization settings.

Creating a team organization#

You get a personal context automatically. Outside any team organization, work uses your own credentials and defaults.

A team organization is created through checkout, not a "create org" button:

• You name the team and start checkout. Checkout does not collect member emails.
• The organization is created in a pending state and stays pending until the checkout completes. It does not become usable until then.
• Once the team plan subscription is active, the organization activates.
• You then invite members from the Members surface.