Your first day running a workspace

This journey is for the person accountable for the workspace. In fifteen minutes you create the organization, connect the provider that makes chat answer, bring in your first teammates, and learn where the governance controls live before you need them.

You need an account on a running instance (quickstart); on a brand-new instance the first account is automatically the Owner, which carries every permission below.

1. 1

   Create the workspace

   If you arrived via the quickstart, your organization already exists — skip to connecting a provider. A fresh sign-in without one lands on the creation wizard: the Organization name is the display name your team sees in the corner of every page — pick something that survives a rebrand. The wizard then offers to connect an AI provider and finishes on the dashboard.

   

2. 2

   Connect an AI provider

   Nothing answers until a provider is connected. If you skipped the wizard's provider step, open Settings > AI providers and click Add provider — paste an OpenRouter key for the widest model catalog, or any OpenAI-compatible provider. A confirmation on the provider row means the key validates; from that moment every agent in the workspace can answer.

   

3. 3

   Bring in the team

   To add people, open Settings > Organization, scroll to the Members section, and click Add member. Each person lands with a role that bounds what they can do: Member reads and chats, Editor builds agents and knowledge, Developer wires up workflows, automations, and API access, Admin runs the workspace. Start people low — raising a role later is one click, and un-leaking access is not.

   

4. 4

   Know where governance lives

   You will not need policies on day one, but you should know the door: Settings > Governance holds audit logs, usage analytics, content policies, guardrails, and retention. The one habit worth starting today is skimming audit logs after the first week — it shows you what your workspace actually does.

Where you are now

The workspace stands: a provider answers, the team is in with bounded roles, and you know where the controls live. The full permission matrix is Members and roles; Admin overview maps every pane you now own; and when compliance asks, governance is the section you show them.