Privacy and control
- Who can use it
- Org admin configures. Everyone is covered.
- Where
- Admin → Settings, Admin → Audit log, Admin → Members, Admin → License
Individual metrics are scoped per role on the server, not just hidden in the page. Team and group numbers stay visible to everyone, with a floor so a small team never exposes one person. This page is the overview. Each control links to its admin page.
Who sees individual metrics
An org admin chooses, per role, who that role can see. Open Admin → Settings → Visibility and joining, under Who can see individual metrics:
- Everyone in the workspace
- Their reporting line
- Their own groups and teams
- Only themselves
Defaults: admins see everyone, managers see their own groups and teams, developers see only themselves. A change applies to the next query. See Visibility.
Minimum group size
A team or group with fewer members than the Minimum group size has its totals and trends hidden from everyone, admins included. The default is 3, and you can choose 1 to 10. Bots and excluded people are not counted. The same floor applies to hierarchy nodes and, with its own minimum, to attribute slices.
Pseudonymous mode
In Pseudonymous mode, names, logins and avatars of other people become a stable pseudonym in every report, export and API response. You still see yourself by name. Choose who sees pseudonyms:
- Off: everyone sees names
- Developers see pseudonyms
- Developers and managers see pseudonyms
- Everyone sees pseudonyms, admins included
Roles and approvals
There are three roles: developer, manager and org admin. Verified members of your GitHub org join as developers when they sign in. Turn on New members wait for approval in the same settings card to hold them as pending until an org admin selects Approve on Admin → Members. Changing a role signs the member out. See Roles and Members.
People without an account can only open an external share link, which gives a read-only viewer session with team and group totals. See Dashboards, alerts and digests.
Audit log
Every privileged action is recorded: who did what, to what, and when. The log is append-only. Org admins open Admin → Audit log, filter by action, actor type, dates (UTC) or text, open a row for its details, and export the filtered result as CSV. See Audit log.
IP allowlist
An org admin can restrict a workspace to your own IP ranges. Sign-in, token refresh and every workspace request from outside the list are refused. An empty list restricts nothing. A downgrade never opens a restriction silently: an org admin clears it.
A key per workspace
Stored credentials and export files are encrypted under a key that belongs to one workspace. The key is destroyed when the workspace is deleted.
Export and erasure
- Workspace export: Admin → License → Workspace data → Request export produces a zip of every dataset as NDJSON and CSV. You get an email when it is ready, and the download is kept for a limited time.
- Exclude a contributor: on Admin → Excluded contributors, Exclude removes a person from every report. Include again brings them back and backfills 90 days.
- Erase a person: Erase permanently deletes every row that identifies them. You type their login to confirm. Pull requests they authored stay without an author. This cannot be undone.
See Data and deletion.
The 30-day read-only window
If a license or trial expires, the workspace falls back to the Free plan and nothing is deleted.
If you uninstall the GitHub App from every integration, the workspace becomes Read-only and shows a deletion date 30 days out. Everything stays readable and exportable. Reinstalling the App restores normal operation. After the window, the workspace is deleted. You can also select Delete workspace immediately.
Accessibility
DevGlimpse targets WCAG 2.1 AA. Every chart has a view-as-table option, and drill-downs work by keyboard. A “Skip to main content” link is the first tab stop. Colour contrast meets AA in both themes.