This path is designed for IT leads, security officers, and workspace administrators. It provides a clear, step-by-step framework to take your enterprise environment from initial setup to a fully governed, production-ready platform.
Set up secure user sign-in and define clear permission levels before inviting team members:
Pilot onboarding — onboard a small group of IT and team leads using direct email invites.
Assign the right access level to each user:
Enterprise Admin
Full control over workspace settings, security policies, user access, and spend.
Team Member
Standard access to run approved tools and workflows, bounded by department permissions and approval rules. Basic access is restricted strictly to their assigned workspace.
3. Connecting business tools and setting access rules
Link your core enterprise software so agents and workflows can interact with them safely:
System integrations — authenticate key company applications and software used by your team.
Connection scope — choose whether a connected tool is available company-wide or restricted to specific departments.
Authentication rules — decide whether tools connect through a shared company service account or require team members to sign in with their personal work accounts.
Establish safety guardrails, approval checkpoints, and spend controls before rolling the platform out to wider teams:
Platform policies — set company-wide AI usage guidelines, tool publishing rules, and risk thresholds. These are found under the Governance tab on your left-side navigation panel.
Approval checkpoints — mark tools request access so members ask before running them, and give agents needs approval guardrails for sensitive actions such as sending external emails or modifying records. Requests are decided in your Requests tab.
Model choices and custom keys — select which AI models your team can use, and connect your company’s custom model API keys if required. Set this under your Governance tab.
Spend controls — turn on the per-run cost cap in the Governance tab so expensive tools need approval, and track spend under Cost Tracking. Per-department budgets are not available yet.