Access & permissions
Chomper controls who can do what at two levels: a role that applies across the whole account, and an optional, per-dashboard allow list for reports that shouldn't be visible to everyone.
Roles
Every user has one of three roles:
| Capability | Admin | Analyst | Viewer |
|---|---|---|---|
| View dashboards | Yes | Yes | Yes |
| Create dashboards, edit panels & layout | Yes | Yes | — |
| View a dashboard's version history, restore a version | Yes | Yes | — |
| Delete a dashboard | Yes | Yes | — |
| Restrict who can see a dashboard | Yes | — | — |
Restricting visibility is Admin-only because it requires the full list of users to choose from, which is itself an Admin-only view — it isn't a stricter rule invented just for dashboards, it follows the same boundary as the rest of the account.
Restricting a dashboard to specific people
By default, every dashboard is visible to everyone on the account. An Admin can turn on Restrict visibility from a dashboard's Access page and pick exactly which Analysts and Viewers are allowed to see it — Admins can always see every dashboard, regardless of that list.
For anyone not on the list, a restricted dashboard behaves exactly as if it didn't exist — it's left out of the catalog, and opening its link directly doesn't reveal that it's there at all. That's a deliberate choice: a restricted report shouldn't even confirm its own existence to someone who isn't supposed to see it, the same way a private document wouldn't announce itself with an “access denied” message.
Note. Restricting a dashboard only changes who can see it — it doesn't change the underlying event data in ClickHouse, and it doesn't affect any other dashboard built from the same data.
Last updated 9 July 2026