Workspace membership and roles
Invite team members, separate personal and work spaces, and prepare for enterprise SSO/SCIM when the account needs procurement.
Loading…
Loading…
Public launch: July 12, 2026 · Team rollout
Teams need the familiar workflow: chats, files, projects, artifacts, apps, and code. AGI adds model routing and explicit policy around Local, BYOK, and Cloud. Website users can try AGI managed Auto Economy with a small free cap. Local and BYOK are supported on desktop and developer surfaces. Higher hosted cloud is invite-only.
Team admin
Invite team members, separate personal and work spaces, and prepare for enterprise SSO/SCIM when the account needs procurement.
Let a workspace require BYOK, allow approved providers only, or keep sensitive projects local until security review clears cloud use.
Enable services at the workspace level while keeping individual authentication and per-tool approval boundaries visible.
Store files, instructions, memory, chats, and artifacts under the workstream so the team does not keep rebuilding context.
Separate AGI-managed spend from provider-paid BYOK and local device work so finance can understand what is happening.
Capture provider labels, tool calls, approvals, shared chats, artifact publishing, and cloud handoffs for review.
Rollout plan
| Phase 1 | Start with Local and BYOK for high-signal users. No managed compute commitment needed. |
| Phase 2 | Enable shared projects, apps/connectors, and provider policy for repeat workflows. |
| Phase 3 | Invite selected users into Cloud for hosted sync, managed compute, and more automated workflows. |
| Phase 4 | Move to enterprise controls when SSO, audit export, retention, and contract terms are required. |
Public launch: July 12, 2026
AGI is designed for the wedge you described: free Local and BYOK adoption first, then invite-only Cloud when users prove demand.