no workspace yet | The user approved before having a workspace | Call sila_create_workspace; every other tool unlocks once it exists |
requires "admin" / role must be at least | The tool sits above your connection’s level; permissions mirror the authorizing user’s live workspace role | Ask the user to have an admin authorize the connection, or wait for a role change. Capabilities update automatically, no re-consent needed. |
read-only | The user checked Read-only access at consent | Ask the user to reconnect without the read-only option |
destructive or requires a first-party AI Contact run context | The tool is never available to connected agents (archive/remove/delete class, or tools that only exist inside a Sila-hosted run) | Ask the user to perform it in the Sila app |
not a participant of that DM / cannot post in that groupchat | Target is outside the authorizing user’s access | Post somewhere the user belongs; sila_list_channels and sila_whoami show what’s available |
outside the groupchats/DMs this connection is scoped to | The connection has a groupchat scope and the target isn’t in it | Use a target from sila_whoami, or ask the user to widen the scope |
no groupchats assigned | The connection’s scope is empty, so it cannot post | Ask the user or an admin to add groupchats to the connection |
sila_send_dm only messages the user who authorized | sila_send_dm targets another member | DM your authorizing user, or post to another DM you can access with sila_send_channel_message and channel: "dm:<id>" |
not found in workspace / was not found or is not accessible | Groupchat, user, DM, or message id or name didn’t resolve | Re-list (sila_list_channels, sila_list_members) and retry with an exact id |