Individual contributor metrics
DX provides settings to manage the visibility of individual contributor (IC) metrics. Use these controls to maintain privacy, limit access by role, and comply with regional regulations.
All settings are located in Access & visibility under Individual metrics visibility.
Visibility settings
Reports
Control who can view IC-level data in the following reports:
- Contributor metrics report
- Interactions report
- Breakdowns by IC
- Work Log by IC
- AI adoption by IC
- AI cost management by IC
To configure, open the Reports dropdown and select an option.
| Option | Behavior |
|---|---|
| Everyone | All users can view IC metrics in reports |
| Everyone but limit visibility to user’s teams | Non-admin users can only view ICs within teams they belong to. |
| Admins and privileged users | Only administrators (snapshot admins, workspace admins, datacloud admins) and users with the privileged role can view IC metrics |
| Admins, privileged users, and team leads | Same as above, plus team leads can view IC metrics |
| Nobody | No users can view IC metrics. Once selected, this setting requires DX support to re-enable. |
Group Dashboard
Control who can view IC breakdowns in the Group dashboard.
To configure, open the Dashboard dropdown and select an option.
| Option | Behavior |
|---|---|
| Everyone | All users can view IC breakdowns |
| Everyone but limit visibility to user’s groups | Non-admin users can only view IC breakdowns for groups they belong to |
| Admins and privileged users | Only administrators and users with the privileged role can view IC breakdowns |
| Admins, privileged users, and team leads | Same as above, plus team managers can view IC breakdowns |
| Nobody | No users can view IC breakdowns. Once selected, this setting requires DX support to re-enable. |
DX AI chat
Control who can view IC-level data in chat sessions with DX AI. This setting applies to both DX AI chat and the Data Studio AI assistant.
To configure, open the DX AI chat dropdown and select an option.
| Option | Behavior |
|---|---|
| Everyone | All users can view IC-level data in AI chat sessions |
| Admins and privileged users | Only administrators (snapshot admins, workspace admins, datacloud admins) and users with the privileged role can view IC-level data |
| Admins, privileged users, and team leads | Same as above, plus team leads can view IC-level data |
| Nobody | No users can view IC-level data in AI chat sessions. Once selected, this setting requires DX support to re-enable. |
AI Code Insights transcripts
Control who can view full AI session transcripts in the Agent Experience Score report.
This setting is only visible when transcript capture is enabled for AI Code Insights.
To configure, open the AI Code Insights transcripts dropdown and select an option.
| Option | Behavior |
|---|---|
| Everyone | All users can view session transcripts |
| Everyone but limit visibility to user’s teams | Non-admin users can only view session transcripts within teams they belong to. |
| Admins and privileged users | Only administrators (snapshot admins, workspace admins, datacloud admins) and users with the privileged role can view session transcripts |
| Admins, privileged users, and team leads | Same as above, plus team leads can view session transcripts |
| Nobody | No users can view session transcripts. Once selected, this setting requires DX support to re-enable. |
De-identifying users
For organizations that need to de-identify individual metrics based on region or policy requirements (such as a Works Council agreement), DX supports selective user de-identification.
Setup
Step 1: Enable protected metrics
- In Access & visibility, scroll to Individual metrics visibility
- Set De-identify protected users to “Enabled”
Step 2: Mark users for de-identification
Set the protected user property to true for each user that needs to be de-identified.
Step 3 (optional): Enable Data Studio warning
For an additional safeguard, enable the Data Studio workers council warning setting. When enabled, DX displays a compliance reminder dialog the first time a user accesses Data Studio in a session. The warning advises users to ensure their analysis complies with local labor laws and data protection regulations, and to consult their HR or legal team if unsure.
How de-identification works
When De-identify protected users is enabled, DX replaces all identifying information for protected users with the label “Hidden” across reports, dashboards, and exports. The following fields are redacted:
- Name
- Email address
- Username / login
- Avatar image
- External profile URLs (e.g., links to source control profiles)
This redaction is applied at the application layer. When DX builds queries and generates report output, it checks the protected flag on each user record and substitutes identifying fields before results are delivered to the UI.
De-identification replaces identifying fields in report output — the underlying data (commits, pull requests, survey responses, etc.) is still processed for aggregate metrics. This means team-level and organization-level metrics remain accurate even when individual users are de-identified.
Drilldown views
When de-identification is enabled, DX also prevents protected users from being found via text search in report drilldowns. Searching for a protected user’s name or email in any report drilldown will return no results for that user.
Reports and dashboards
De-identification applies to all IC-level views, including:
- Contributor metrics
- Interactions report
- Breakdowns by IC
- Work Log by IC
- AI adoption by IC
- AI cost management by IC
- Group dashboard IC breakdowns
- SLA breakdowns
In each case, the protected user’s row still appears in results (so aggregate counts remain correct), but identifying fields display as “Hidden”
DX AI
DX AI features that surface data within standard reports (such as AI-generated summaries or analysis) respect the same de-identification controls. Protected user names and emails are not exposed in AI-generated output within DX reports.
Data Studio considerations
Data Studio allows users with access to write and run custom SQL queries. Because these queries run directly against the underlying data, the application-layer redaction described above does not apply to Data Studio query results. Users with Data Studio access may be able to query tables that contain identifying information for all users, including protected users.
To manage this, DX provides the following controls:
| Control | Description |
|---|---|
| Data Studio visibility | Restricts who can access Data Studio. Configure under Access & visibility. |
| Data Studio workers council warning | Displays a compliance reminder when users first access Data Studio in a session, advising them to ensure their queries comply with local regulations. |
| Role-based access | Only users with appropriate roles can access Data Studio. |
If your organization requires that protected users cannot be identified under any circumstances, restrict Data Studio access to a trusted set of administrators using the Data Studio visibility setting.