Getting started

This walkthrough takes a brand-new organization to a working setup: people invited, groups assigned, company tools connected, and the first task running. Everything here lives in the admin sidebar (the Org section) — you need the admin role, which the first person from your email domain gets automatically.

1. Add people

Admin → Members.

1. In Invite people, enter a work email, pick the role (member / admin), press Send invite. The link is copied to your clipboard — paste it to the person in Slack or email.
2. Invites work for contractors outside your email domain too — the invite pins them to your org with the role you chose.
3. Pending invites appear in the members table with an invited · Nd left status. Links expire after 7 days; copy link re-copies it, revoke kills it immediately. Expired invites are marked and can be removed.
4. People from your email domain can also just sign in — they join your org automatically as members.

Per-person controls in the table: role, permission to register own MCP servers, daily/weekly token caps. Click a row to expand everything the person can reach (connectors, custom MCP servers, skills — each labelled whole org / via group / direct) and to grant custom MCP servers or skills directly.

2. Create groups and assign people

Admin → Groups.

1. Type a name (Sales, Engineering, Compliance…) → Create group.
2. On the group card tick Members (there’s a search box; current members sort first). Or do it from the other side: Members → Groups column → click the chips and tick groups in the popover.
3. A person in several groups gets the union of their access.

What a group carries (all three columns on the group card):

Column	Meaning
Company services (personal auth)	Catalog connectors scoped to this group — each member connects with their own account. A service with no group ticked anywhere stays visible to the whole org.
Custom MCP servers (vault)	Org-registered MCP servers this group may use through the shared, hidden credential.
Skills	Skill packs shared to this group.

If you use SSO, groups can also come from Okta — see Single sign-on: IdP-sourced groups are matched by name, badged from IdP, and their membership follows the IdP on every login.

3. Connect company tools

Admin → Connectors. Two layers:

The catalog (official services)

Click a service row (Notion, Slack, Jira, YouTrack, Salesforce…) to open its config. Choose, per service, how people connect — both can be on:

• OAuth sign-in — each person goes through the vendor’s consent screen. Works out of the box via a shared app where the vendor supports dynamic registration; for tighter control, register your own OAuth app in the vendor console (the config panel shows the exact redirect URI and a per-vendor step-by-step guide, expanded by default) — then the vendor admin can approve exactly one app.
• Shared org token — paste one company credential (a service account / bot token). It is stored encrypted; every allowed person connects in one click and never sees the token. Right for wikis and knowledge bases.

Also on the panel: instance URL (for self-hosted vendors), and visibility by groups. If the service needs a paid seat or a vendor-side admin, enable it first — people see it as needs admin setup until then.

Custom MCP servers

The bottom of the same tab. + Add org connector registers any MCP endpoint (HTTP/SSE URL or a stdio command), with a data class label and an encrypted credential. Access is granted per person (checkbox grants on the card) or per group. Members run through it without seeing the secret.

What members do

Each person opens Connectors (user section) and connects their own accounts: one click for org-token services, the vendor consent screen for OAuth, or paste a personal token (PAT) where the service supports it. The Missing a tool? card routes requests to you.

4. Run the first task

Back on Tasks (home): type what you would hand a colleague, check the connector chips under the composer, send with ⌘↵. Watch the live session; when it’s good, hit Make it a process — and later wire that process to a schedule under Automations.

5. Before inviting the whole company

• Models & limits — add the org model key (trial credit is small), pick the default model, confirm spend caps.
• Security → Policies — the built-ins are on; add custom rules with the constructor once real traffic accumulates.
• Security → Routing — point high-severity alerts at Slack.