Overview
Roll out Proliferate across a team — organization setup, managed authentication policy, integrations, security, and usage.
How to roll Proliferate out across a team: repository access, authentication policy, integrations, secrets, and 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 member's sessions get.
- Invite a pilot group, then the broader team. Have the pilot group sign in and run real work before inviting everyone.
- Set limits and monitor usage. Track model spend, and see where limits are enforced today versus left to your own provider or gateway.
Sections#
Organization
Members, roles, and the GitHub App.
Agents & model access
Which managed authentication routes members may newly configure, and how they authenticate to models.
Integrations
Govern the tools agents can use org-wide, and register custom MCP servers.
Security
What's enforced, what's user-controlled, and where the isolation boundaries sit.
Usage & billing
Plans, metered resources, and where billing is managed.
Member-facing docs live in Proliferate docs. Self-hosting setup lives in Self hosting.