Skip to content

Visibility and privacy controls

By plan Org adminManager
Who can change it
Org admin (managers see the settings read-only)
Where
Admin → Settings → Visibility and joining

DevGlimpse never ranks people. Team and group numbers are visible to everyone. Individual numbers follow rules you set per role, and the server enforces them. This page covers the settings that control that.

Choose who can see individual metrics

  1. Go to Admin → Settings.
  2. Under Who can see individual metrics, set a scope for Admins, Managers and Developers.
  3. Click Save settings.

The scopes are:

  • Everyone in the workspace
  • Their own groups and teams
  • Their reporting line, which is everyone below them on the manager chain
  • Only themselves

Defaults: admins see everyone, managers see their own groups and teams, developers see only themselves.

The change applies on the next request. You do not need to redeploy or ask people to sign in again.

Set a minimum group size

Minimum group size hides the totals and trends of any team or group with fewer members than the number you pick. Bots and excluded people are not counted. The numbers are hidden from everyone, admins included, so no one can be singled out.

  1. In Admin → Settings, open Minimum group size.
  2. Pick a value from 1 contributor (no minimum) to 10 contributors.
  3. Click Save settings.

The default is 3.

Pseudonymous mode

By plan Pseudonymous mode is included with some plans. Check Admin → License → Plan features.

In pseudonymous mode, the names, logins and avatars of other people are replaced by a stable pseudonym in every report, export and API response. Everyone still sees themselves by name.

Pick who it applies to under Pseudonymous mode:

  • Off: everyone sees names (the default)
  • Developers see pseudonyms
  • Developers and managers see pseudonyms
  • Everyone sees pseudonyms, admins included

IP allowlist

By plan The IP allowlist is included with some plans. Check Admin → License → Plan features.

An IP allowlist restricts access to your workspace to the networks you list. When the list is empty, nothing is restricted. When it is set:

  • sign-in and token refresh are refused from outside the list;
  • a session already open stops working from outside the list within about 15 minutes;
  • the public API and MCP server are refused from outside the list.

You can list single addresses or networks in CIDR notation, IPv4 or IPv6, up to 100 entries. You cannot save a list that blocks the address you are working from, so you cannot lock yourself out. Every change is recorded in the audit log.

If you downgrade, an existing list stays in force until an org admin clears it. Clearing a list is always allowed.

Setup screen coming This works in DevGlimpse today, but its setup screen is not in the app yet. Contact support if you need it before then.

Common questions

A manager cannot see a developer's numbers.Check the manager's scope. The default is Their own groups and teams, so the developer must be in one of the manager's groups or teams. Also check the minimum group size.
Can an admin see everything regardless of settings?No. An admin follows the scope set for admins, and a team below the minimum group size is hidden from admins too.