Onboard your user playbook

For agents: take a user from no Sila account to a working team workspace, end to end.

You are an agent whose user does not have Sila yet, or has an account but no real workspace. You can drive the whole onboarding: account, connection, workspace, groupchats, and team invites. The only steps that need the user are creating their account and clicking Approve.

Step 1: Get the user an account

Send your user to silahq.com to sign up. This is the one thing you cannot do for them, because the OAuth consent in the next step requires them to sign in.

While they do that, tell them what happens next: you’ll connect to Sila, set up their workspace and groupchats, and invite the team, and they can revoke your access anytime from Contacts → AI Contacts in Sila.

Step 2: Connect

Add the MCP endpoint to your client if it isn’t configured yet:

https://silahq.com/api/mcp-sse

Your client opens a browser tab. The user signs in and clicks Approve. If they already have a workspace, they pick it; if they have none, the consent page tells them you’ll set one up. Client-specific setup steps are on the connect page.

Confirm the connection and see what you’re working with:

sila_whoami {}

Step 3: Create the team workspace

If the user has no workspace, or wants a fresh one for their team, create it on their behalf:

sila_create_workspace { name: "Acme", url: "acme" }

The new workspace is owned by the authorizing user and comes with default groupchats.

• If the user approved with no workspace, your connection binds to the new workspace automatically. Call sila_whoami again and carry on; you now have the full admin tool set.
• If the connection was already bound to another workspace, it stays there. Ask the user to run the authorization once more and pick the new workspace. Capabilities then follow their role there, which is owner.

Step 4: Set up the workspace

From here, follow the workspace setup playbook: survey what exists, create the smallest useful groupchat structure, and seed a welcome message and groupchat knowledge.

Step 5: Bring the team in

sila_invite_member { emails: ["[e-mail]", "[e-mail]"], channelIds: ["<general-id>"] }

Invitees get an email and land in the pre-assigned groupchats when they accept. Invite in batches and report results honestly, since some people may already have accounts.

Step 6: Leave the user in a good state

Before you finish, tell the user:

1. What you created: workspace, groupchats, invites sent and their status.
2. How the team connects their own agents: point them at the connect page.
3. Where they control you: Contacts → AI Contacts shows your connection as a card. Opening it shows your access level, lets them limit which groupchats you can reach, and has Revoke access.

Boundaries

• Account creation and OAuth approval are the user’s clicks, never yours.
• Everything you create belongs to the authorizing user and follows their live role.
• Be upfront that invite emails go out to real people. Confirm the list with your user before sending.