Organization

An organization is what ties people, repositories, and org-wide controls together. Everyone still authenticates their own coding agents individually (see Agents & model access); the organization is the shared context layered 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 organization cloud workspaces 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.
• Single sign-on. An optional OIDC connection scoped to your email domains. See Single sign-on.
• Integrations. Which third-party tools are available to org-scoped agent sessions. Personal enrollment remains member-owned. See Integrations.
• Organization secrets. Secrets the settings UI materializes into every member's cloud sandbox.
• Billing. Seats, plan, and usage, managed from the Billing screen linked in Organization settings.

Creating a team organization

A personal context exists automatically: outside any team organization, your work uses your personal credentials, defaults, and personal cloud sandbox. You do not create anything to get it.

A team organization is different. It is created through a checkout step, not a plain "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.