---
title: "What are ungrouped users?"
canonical_url: "https://docs.getdx.com/knowledgebase/what-are-ungrouped-users/"
md_url: "https://docs.getdx.com/knowledgebase/what-are-ungrouped-users.md"
last_updated: "2026-09-03"
---

# What are ungrouped users?
Each DX organization has a mapping of user identities in the [Organization view](https://app.getdx.com/organization/users/unlinked). It lists out each DX user, alongside their corresponding identity in every third-party platform you've connected:

![Unlinked users view](https://docs.getdx.com/assets/images/knowledgebase/what-are-ungrouped-users/user-linking.png)

When a connector ingests data, it uses that mapping to tie the data back to a DX user. The flow looks like:

- A piece of data (e.g. a pull request or a deployment) is ingested from a third-party tool, and DX looks at the user or author associated with that data
- DX finds that user’s username in the third-party tool
- DX looks for a DX user mapped to that username
- DX attributes the data to that DX user
- If that user belongs to a team in DX, the associated metrics roll up to the user’s team - this is how team rollups are calculated

However:

- **If that user does not belong to a team in DX**, their data is considered ungrouped, and will appear in its own row in team rollup reports.
- **If DX cannot find a DX user that is mapped to the third-party username associated with the data**, their data is also considered ungrouped.
- **If the ingested data did not have any user associated with it** or we were not able to read/parse the user’s identity, the data is considered ungrouped.

In reports, data is broken down by team, with a separate Ungrouped row for any data that couldn't be tied back to a DX user. **All data received by the connector is displayed in the report’s trend chart and aggregate metrics**, regardless of whether it can be attributed to a user.
---

## Sitemap

[Overview of all docs pages](/llms.txt)