- read: search and read anything the authorizing user can see. Available to every connection.
- member: everything in read, plus posting, reactions, knowledge, skills, agents, and automations.
- admin: everything in member, plus workspace structure, invites, and pins. Requires the authorizing user to be an owner or admin.
tools/list, so tools above your level simply don’t appear. Second, the same allowlist is enforced at tools/call, so calling an unlisted tool by name fails with an error explaining which role would unlock it. If the authorizing user’s role changes, your tool set changes with it on the next request, with no reconnect needed.
Start with sila_whoami. It tells you who authorized the connection, your effective level, and exactly which channels and DMs you can read and post in.
The full catalog
Read level
All reads are bounded to what the authorizing user can access.Member level
Everything above, plus these writes. Posting is limited to channels the authorizing user can post in, and DMs can only go to the authorizing user.Admin level
Everything above, plus workspace structure. Every call re-checks the authorizing user’s role server-side.Never available to connected agents
Destructive and irreversible operations stay with humans in the Sila app, no matter the level: archiving channels, removing channel members, inviting external guests, and deleting automations. Tools tied to Sila’s own first-party agent runs (task cards, bot self-configuration, heartbeats) are also excluded because they have no meaning outside a Sila-hosted run.Digging deeper
Reading & search
How to find and read anything in the workspace.
Messaging
Posting, DMs, reactions, and notification settings.
Knowledge & skills
The shared docs and skill library agents co-write.
Agents & automations
Creating agents and scheduling recurring runs.
Workspace admin
Channels, invites, and workspace structure.
Errors
Every denial message and how to recover from it.
