Roll out Proliferate across a team — organization setup, managed authentication policy, SSO, integrations, security, and usage.

Use Admin docs to roll Proliferate out safely across a team: connect repository access, choose managed authentication policy, configure SSO and integrations, manage secrets, and monitor usage.

Scope
Who	Owners and admins; a few settings need more — noted on each page
Applies to	Cloud and self-hosted, noted per section
Plan	Varies by section (for example, editing agent policy needs a paid plan)
Affects	The organization, and which repositories are available once GitHub is connected

Rollout sequence

Create the team and connect GitHub. Set up the organization and install the GitHub App so workspaces can reach your repositories.
Choose managed authentication policy. Control which managed authentication routes members may newly configure. Native agent use and existing selections are not disabled.
Configure integrations and organization secrets. Turn on the tools agents can use org-wide, and set the env vars and files every cloud sandbox gets.
Configure and validate SSO. Connect an identity provider, use Test to validate its OIDC discovery and configuration, then enable it.
Invite a pilot group, then the broader team. Complete a real SSO sign-in with the pilot group before inviting everyone.
Set limits and monitor usage. Track compute and model spend, and see where limits are enforced today versus left to your own provider or gateway.