Skip to main content

Who Can Do What

The full reference for who can do what. For a short introduction to levels, grants and verification, read Workspaces first. In the app, each person's access is shown as a computed view of these rules.


How to read the tableโ€‹

  • The first three columns are the governance ladder. Everyone with a seat sits on exactly one of them. A Channel admin has no seat: see Channel admins below.
  • The + Tickets, + X, + Messages and + Knowledge columns show only what the grant adds to a Member. Owners and Admins already hold every grant by role, so a grant never changes anything for them.
  • The last column shows what an active verification adds on top, and only for the specific channels you're verified on.
  • A dash means that column changes nothing for that row.
SurfaceOwnerAdminMember+ Tickets+ X+ Messages+ KnowledgeVerified admin (adds)
Analytics and the members leaderboardโœ…โœ…โœ…-----
Ask AI, including running queriesโœ…โœ…โœ…-----
Reports (view, and create, schedule and share your own)โœ…โœ…โœ…-----
Inbox (view)โœ…โœ…โœ…-----
Inbox (resolve alerts)โœ…โœ…โŒ----Scoped ยน
Tickets (the unified queue)โœ…โœ…โŒโœ… workspace-wide---Scoped ยน
Knowledge Base (read every tab, test answers)โœ…โœ…โœ…-----
Knowledge Base (review an item you're asked to review)โœ…โœ…โœ…-----
Knowledge Base (manage: sources, items, collections, reviews, Gaps, Knowledge access, ticket macros)โœ…โœ…โŒ---โœ…โŒ โน
Audit logโœ…โœ…โœ…-----
Agent and moderation config, Telegram and DiscordVerified ยฒVerified ยฒVerified ยฒ----Scoped ยน
X configuration: Messages, Listening, Safety, Agent Settingsโœ…โœ…โŒ-โœ…--n/a ยณ
Send messages as a channel's agent from Ask AI (post, private message, delete what Ask AI sent)โœ…โœ…โŒ--โœ…-โŒ โธ
View the team rosterโœ…โœ…โœ…-----
Team management (invite, remove, change level, assign grants)โœ…โœ… limited โดโŒ-----
Access requests (view and approve)โœ…โœ…โŒ-----
Approved domainsโœ…โœ…โŒ-----
Billing and subscriptionโœ…โœ…โŒ-----
Integrations (Slack and other alert destinations)โœ…โœ…โŒ----โŒ โต
Connect, assign, unlink or claim a channelโœ…โœ…โŒ----โŒ โถ
Workspace settings (view)โœ…โœ…โœ…-----
Workspace settings (change)โœ…โœ…โŒ-----
See a teammate's two-factor statusโœ…โŒโŒ-----
Permanently delete a channelโœ…โŒโŒ-----
Restore or import a server backup (Discord)โœ…โŒโŒ-----
Grant or revoke Adminโœ…โŒโŒ-----
Transfer ownershipโœ…โŒโŒ-----
Delete the workspaceโœ…โŒโŒ-----
Leave the workspaceโŒ โทโœ…โœ…-----

ยน Scoped to the specific channels where you hold an active verified admin status, not the whole workspace. ยฒ Configuring the agent for a channel requires an active verified admin status on that channel. This applies to everyone, the Owner included. See Even Owners verify. ยณ X accounts carry no verification at all, so there is no verified arm here. X access is a workspace level, or the + X grant, and nothing else. โด Admins invite and manage Members, including assigning grants and including grants in invitations. They cannot change the Owner, another Admin, or the Admin level itself. โต Alert destinations are workspace-wide delivery configuration rather than channel data, so verification doesn't reach them. It's Owner and Admin only. โถ Being a verified admin of a channel doesn't let you take it out of a workspace you can't manage. Ask the Owner or an Admin, or wait for the 30-day automatic detach. See Detaching Channels. โท The Owner must transfer ownership or delete the workspace before they can leave. โธ Verification never confers sending as the agent: posting publicly as the brand needs a governance level or the + Messages grant. See + Messages. โน Knowledge is workspace-level, so verification doesn't open it. A verified admin without + Knowledge keeps only one per-channel setting: which admins' messages their channel captures into the Knowledge Base. See + Knowledge.


Two rules explain almost every cellโ€‹

Every workspace member reads. Analytics, Ask AI (including running your own queries), reports, the inbox, the knowledge base, the audit log, the team roster and workspace settings are visible workspace-wide to everyone with a seat.

Changes follow the level, a grant, or verification. Settings, billing, team management, resolving inbox alerts and managing the knowledge base belong to the Owner and Admins. Agent and moderation configuration for a channel belongs to whoever is verified on it. Tickets, X, sending messages as the agent and the knowledge base are the four places a grant can give a Member write access.


The exceptions to universal readโ€‹

Two surfaces are not open to every member.

The unified ticket queue. Three things open it: an Owner or Admin level, the + Tickets grant (which opens every channel in the workspace), or a verification (which opens only the channels you're verified on). A verified admin sees a Filtered badge, because they only see their own channels' tickets.

X configuration. The X configuration pages are locked for a Member until they hold the + X grant. X data (the account's overview, inbox, reports, Ask AI and audit log) stays open to every member.


Channel pagesโ€‹

Any workspace member can open a channel's Overview from its row under Channels in the sidebar, and read its inbox, Ask AI, reports, analytics, members and audit log on the workspace pages filtered to that channel. Without a verification for that channel you'll see a "Viewing as a workspace member" banner with a Verify to manage button, and the configuration pages stay locked.

Locked pages are never hidden. They stay listed, and hovering the lock says what's missing: "Verify your admin status in this channel to unlock." for Telegram and Discord, or "Requires the X grant. Ask a workspace owner or admin." for an X account.

Channel adminsโ€‹

A Channel admin joined by verifying on one of the workspace's Telegram groups or Discord servers and has no seat yet. Read the Member column, narrowed to the channels they hold a fresh verification on, with these differences:

  • Every read surface (Overview, Inbox, Ask AI, Reports, Analytics, Audit Log, the Channels list) shows only their channels.
  • Grants never apply, so the grant columns don't reach them; they read the knowledge base without editing it.
  • The Team, workspace settings and Integrations pages aren't shown.
  • The verified-admin column applies as usual on their channels.

Request wider access, on the notice they see on every workspace page, asks for a seat. See Joining as a channel admin.


Next stepsโ€‹