Skip to content
Start free
Product Demo Pricing Security Docs Changelog Start free

People and identities

Org adminManager
Who can link or split people
Org admin
Attributes upload
CSV, up to 2,000 rows and 1 MiB

A person often has more than one identity: one on GitHub, one on GitLab, a second login for a contractor account. DevGlimpse calls each identity a contributor and ties the ones that belong to the same human into one person, so their numbers are not split.

One person across providers

DevGlimpse links contributors automatically when they share the same verified email address. Team and group numbers then count the person once, even if several of their identities belong to the same team.

An org admin can also link by hand:

  • Merge. Link two to twenty contributors into one person. All identities of the people involved become one.
  • Split. Take one contributor out of its person. An automatic email link never puts it back.

Both actions are recorded in the audit log. A merge that would make a person their own manager is refused.

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.
Note Individual rows stay per identity. Team, group and minimum group size calculations count distinct people.

Bots

Bot accounts are left out of every metric. A bot’s pull requests, reviews and commits never count toward cycle time, throughput or review numbers for people. The one exception is AI agents. Their work is counted in their own AI columns, so you can compare AI-authored work with human work without inflating anyone’s numbers. Bots do not count toward the minimum group size.

Excluding people

An org admin can keep people out of every report, for example contractors or service accounts, under Admin → Excluded contributors. An excluded person’s activity is removed and is not synced again. Including them again starts a backfill that brings their history back. The same page offers permanent erasure, which asks you to type the person’s login to confirm.

Contributor attributes from a CSV

Attributes describe people for slicing reports, such as employment type, level or location. An org admin defines them and can load values for many people at once from a CSV file.

  1. Make a CSV whose first column is login. Each other column heading is an attribute key your workspace defines.
  2. Add one row per contributor. An empty cell leaves that value unchanged.
  3. DevGlimpse checks every row before writing anything.

If any row has a problem, nothing is applied, and DevGlimpse lists each problem with its row. The header is row 1. Files are limited to 2,000 rows and 1 MiB.

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.

Once attributes exist, the Attributes report groups delivery by an attribute under Add filter → Group by. A slice with fewer people than the workspace’s minimum slice size is hidden from everyone.

Reporting lines

If you maintain a reporting structure, an org admin can enter it under Admin → Hierarchy, by hand or from a CSV. It powers the Their reporting line visibility scope. See Roles.