Who can see usage
Usage visibility depends on role:| Viewer | What they can see |
|---|---|
| Global admin | All workspace activity |
| Scope admin | Activity for the scopes they manage, plus their own runs elsewhere |
| Member | Their own runs only |
What the table shows
| Column | What it shows | Example |
|---|---|---|
| Run At | When the Slack Agent run happened | Apr 3, 2025 2:22 PM |
| Scope | The resolved scope name for that run | Base Scope or frontend-team |
| Triggered By | The Slack user who started it | @jane |
| Thread | Links to the original Slack conversation and the thread review UI | Slack link + review link |
Human vs. automation runs
Usage shows both human-triggered and automation-triggered runs in the same view:- Human runs appear when someone mentions
@coderabbit, uses a slash command, or interacts with a Slack surface. - Automation runs appear on their configured schedule. They show the automation name and the channel where they ran.
Common actions from Usage
From the Usage view, teams can:- Open the related thread review for full run detail
- Jump back to the original Slack conversation
- Confirm which scope handled a request
- Review recent workspace activity without searching Slack first
- Trace an unexpected result back to its scope, triggering user, and execution detail
Filtering and navigation
The Usage view supports text search across scope names and triggering users, scope-based filtering to focus on a specific team or channel, and sorting by time, scope, or user. Results are paginated so you can browse recent and historical runs without loading everything at once.What’s next
Thread reviews
Open a run in detail when you need to inspect context, diffs, and execution history.
Admin roles and security
Review how activity visibility changes for global admins, scope admins, and individual members.
Automations
Use activity history to understand how recurring Slack Agent work is behaving after rollout.