Roles and visibility
- Roles
- Developer, Manager, Org admin, Viewer (share links only)
- Where to change visibility
- Admin → Settings
- Default minimum group size
- 3
Every person in a workspace has one role. The role decides which admin pages they can open and how much individual data they can see. Team and group numbers are visible to everyone, so people can see how the team is doing without anyone being singled out.
The roles
- Developer. Reads dashboards and reports. Cannot open the Admin area. This is the default role for people who join.
- Manager. Everything a developer can do, plus custom groups, sync runs, alerts, share links and a read-only view of members and settings.
- Org admin. Full access: members and roles, integrations, license, visibility settings, audit log, export and deletion. Shown as Admin next to the workspace name.
- Viewer. A read-only role for people without an account who open a share link. A viewer is never a member of the workspace and cannot be assigned. A viewer sees team and group aggregates for the one shared dashboard, never individuals.
You can see your own role next to the workspace name at the top of the left navigation.
Who can do what
| Task | Developer | Manager | Org admin |
|---|---|---|---|
| View dashboards and reports | Yes | Yes | Yes |
| See team and group aggregates | Yes | Yes | Yes |
| See individual metrics | Own by default | Own groups by default | Everyone by default |
| Open the Admin area | No | Yes | Yes |
| Open Groups | No | Yes | Yes |
| View Members | No | Yes | Yes |
| Approve members, change roles, invite | No | No | Yes |
| View Integrations and Sync runs | No | Yes | Yes |
| Connect organizations, change repositories synced | No | No | Yes |
| Open Alerts | No | Yes | Yes |
| Create share links | No | Own dashboards | Any dashboard |
| Open Settings (visibility, approval) | No | Yes | Yes |
| License, export and delete workspace | No | No | Yes |
| Audit log, Hierarchy, Excluded contributors | No | No | Yes |
Individual metric visibility
Individual metrics are the numbers about one person. Each role has a scope, set under Admin → Settings → Visibility and joining → Who can see individual metrics.
| Scope | What it means | Default for |
|---|---|---|
| Everyone in the workspace | Sees every individual’s metrics | Admins |
| Their own groups and teams | Sees people in the groups and teams they belong to | Managers |
| Their reporting line | Sees the people below them on the manager chain, plus themselves | No role |
| Only themselves | Sees only their own metrics | Developers |
The server enforces the scope on every query. A person outside their scope gets fewer rows, not hidden columns. Everyone can always see their own numbers.
Their reporting line uses the manager chain that an org admin sets under Admin → Hierarchy, by hand or from a CSV. A manager sees everyone who reports to them, directly or through others. It does not use the department tree.
Minimum group size
A team or group with fewer people than the minimum has its totals and trends hidden from everyone, admins included. This stops a small group from exposing one person. Set it under Admin → Settings → Minimum group size, from 1 to 10 contributors. The default is 3. Bots and excluded people do not count toward the size. A person linked across several providers counts once.
DevGlimpse also withholds a group when it could be worked out by subtracting a larger group from a smaller one.
Pseudonymous mode
Under Admin → Settings, Pseudonymous mode replaces the names, logins and avatars of other people with a stable pseudonym in every report, export and API response. Choose who it applies to: Developers see pseudonyms, Developers and managers see pseudonyms, or Everyone sees pseudonyms, admins included. Everyone still sees themselves by name.