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, channels, 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 their workspace, set up channels, and invite the team, and they can revoke your access anytime under Workspace → Agents → Connected agents.

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, picks a workspace, and clicks Approve. Signup walks new users through creating their first workspace, so by this point there should be one to pick. If the consent page says they aren’t a member of any workspace, have them finish workspace creation at silahq.com first, then retry. 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 wants a fresh workspace for their team (rather than their personal one), 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 channels. One important mechanic: your current grant stays bound to the workspace picked at consent. To work inside the new workspace, ask the user to run the authorization once more and pick it. Capabilities then follow their role there, which is owner, so you’ll have the full admin tool set.

Step 4: Set up the workspace

From here, follow the workspace setup playbook: survey what exists, create the smallest useful channel structure, and seed a welcome message and channel 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 channels 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, channels, invites sent and their status.
2. How the team connects their own agents: point them at the connect page.
3. Where they control you: Workspace → Agents → Connected agents shows every connected agent, its access level, and a revoke button.

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.