Organization
The Organization view helps you understand and maintain the people structure DX uses for reporting, rollups, and snapshots.
Use the Organization view after your team hierarchy already exists in DX. It is not the first-time setup path for importing or rebuilding your org structure. For initial setup or bulk changes, start with Team hierarchies, where you can upload, preview, and publish hierarchy data.

Overview
The view is organized into three tabs:
- Teams: The formal hierarchy DX uses for team leads, team membership, reporting rollups, snapshot participation, and ownership.
- Groups: Flexible collections of users for reporting or coordination. Groups can be managed by hand or linked to teams so membership stays in sync.
- Users: The people in your DX account, including their team assignment, groups, attributes, snapshot status, and linked source-control accounts.
Teams
Use Teams when you need to inspect or maintain the formal org structure that powers DX rollups.
Teams are arranged in a hierarchy. A parent team rolls up the teams beneath it, so changes to team placement can affect how data appears across reports. Each team has one team lead. Team leads can manage more than one team, and a team lead is not counted as a team member unless they are also assigned to a team.
Users can only be assigned to one team in DX. If someone works across several teams, assign them to the parent team that best represents their work, or use Groups and attributes to create flexible views.
In the Teams tab, you can:
- Browse All teams or Your teams.
- Search the hierarchy and expand matching branches.
- Create a team, edit team details, or add sub-teams.
- Add or remove members.
- Include or exclude members from snapshots.
- Download the team hierarchy as a CSV.
- Open the team audit log to see recent team changes.
- Edit Software catalog properties and aliases for eligible leaf teams.

Your teams
Your teams shows teams you lead or belong to, plus the teams beneath them. DX re-roots that view so you can focus on the part of the hierarchy that matters to you, without showing unrelated ancestors or sibling teams.
Snapshot impact
Team and member updates can affect active or upcoming snapshots. Excluding someone from snapshots prevents them from being included in current and future snapshot participation. Deleting a team preserves historical snapshot data, but parent teams with child teams must have those child teams reassigned.
For bulk hierarchy changes, use Team hierarchies instead of editing team-by-team in Organization.
Groups
Use Groups when you need a flexible set of users that does not map cleanly to your formal org chart.
Groups are useful for initiatives, programs, temporary project teams, communities of practice, or any view that cuts across the official hierarchy.
There are two ways to manage group membership:
- Manual groups: Add or remove members directly.
- Linked-team groups: Link one or more teams. DX syncs everyone on those teams into the group and keeps membership up to date as the teams change.

Manual vs linked groups
Manual groups are best when membership is curated and changes occasionally.
Linked-team groups are best when the group should always match one or more teams. When a group is linked to teams, its members cannot be edited by hand. To change membership, edit the linked teams or unlink the group.
Groups can have up to 500 members.
Users
Use Users when you need to find a person, check their team or group membership, or update the user data that helps DX connect activity across systems.
The Users tab shows all non-deleted users in the account. The headline count only includes users assigned to a team. Users without a team can still appear in the list, but they are not included in that count.
In the Users tab, you can:
- Search by name or email.
- Filter by team, including everyone in that team’s subtree.
- Download a CSV of the current search and filters.
- Open a user profile.
- Update team assignment, start date, and linked GitHub or GitLab usernames.
- View or edit visible custom attributes.
- Remove a user from ad-hoc groups.
- Include or exclude a user from snapshots.

Linked accounts and attributes
GitHub and GitLab usernames help DX connect users to source-control activity. Each username can only belong to one user in an account.
Custom attributes help you filter and break down reports by dimensions such as job level, location, employment type, or tool usage. For bulk attribute management, use Custom user attributes. For property definitions like startdate, githubusername, and excludefromsnapshots, see User properties.
Permissions
If you can view Organization but cannot make a change, check the type of change first:
- Teams: Creating, deleting, and saving team changes depend on your account’s team-editing mode. Your workspace may allow edits for everyone, admins only, team leads and admins, or no one.
- Groups: Snapshot admins, workspace admins, and Data Cloud admins can create and manage groups. Group owners can edit the groups they own.
- Attributes: You can only edit attributes that are visible to you. Some attributes are privileged and only appear for admins or privileged users.
- Software catalog fields: Properties and aliases only appear for eligible leaf teams with a Catalog team entity. If they appear in Organization, editing them follows the same permission as other team edits.
If an action is missing, start with the owner of that area: a workspace admin for team-editing access, the group owner for a group, or an admin for privileged attributes.