Why this matters
Pensero connects activity from third-party tools to a person's profile using usernames. GitHub handles, GitLab usernames, YouTrack accounts, Jira users, AI tool accounts.
If a username is wrong, missing, or outdated, that person's work does not appear in their data. Their delivery score looks low. Their AI impact looks empty. None of it reflects what they actually did.
This is the second thing to check when a team member's numbers look off. Check repositories first. If those are fine, come here.
How to check a person's integration mapping
Step 1: Open the People page
Go to Pensero and click People in the left sidebar.
Find the team member and click their name.
Step 2: Check their repository activity
Inside their profile, click the Repositories tab.
You will see a list of repositories where Pensero has recorded activity for this person.
Ask yourself: is the repository where this person works listed here? Do the PRs merged number look right for the period you are reviewing?
Check repository branch configuration
A repository can be connected correctly but still show low or missing activity if Pensero is not tracking the branch where work is happening.
For repositories without pull requests or merge requests, Pensero treats the repo as trunk-based and tracks commits merged into the configured default branch.
For example, if a team works in dev or staging but Pensero tracks master, activity may not appear until the work is merged into master.
How to fix it for trunk-based repositories
If the team mainly works from another branch, update the tracked/default branch for that repository in Pensero so it matches where work actually lands.
To make this change, you need access to the repository integration settings. This is usually available to organization admins.
Go to Integrations > Code Repositories, select the relevant repository, then click the Edit button next to the trunk-based configuration.
If you do not have access, contact your Pensero admin or reach out to Pensero through the product chat with:
Repository name
Current branch being tracked
Branch where active work lands
Whether the repo uses PRs/MRs or trunk-based development
Pensero can then confirm the correct setup and update the tracked branch if needed.
If the repository is listed but shows 0 PRs merged, the repository is connected but this person is not being matched to it. That is a username issue. Continue to Step 3.
Step 3: Check their integrations
Inside the same profile, click the Integrations tab.
You will see a table of connected tools and the username linked to this person for each one.
Each person in Pensero needs three types of accounts correctly mapped.
A repository account (GitHub, GitLab, BitBucket) so their pull requests are attributed to them.
A ticketing account (Jira, YouTrack, Linear) so their tickets and cycle time data are linked.
And an AI tool account (GitHub Copilot, Claude Code, Cursor, or other AI coding tools) so their AI Impact data is captured. If any of these are missing or incorrect, that part of their work will not appear in Pensero.
Pensero supports multiple mappings per person, including multiple mappings within the same integration. For example, one user can have several AI tools linked at the same time, such as Claude and Cursor, and can also have multiple GitHub usernames connected to the same Pensero profile.
What to look for
A username is missing entirely. The integration is listed but the field is empty.
The username shown does not match what this person actually uses in that tool.
The username refers to a personal account instead of the organization account.
Common example: an engineer has both a personal GitHub account and an organization GitHub account. If the personal handle is mapped, none of their organization work will be attributed. The fix is to update the mapping to the organization handle.
What to do when you find an issue
Managers can add or edit usernames directly in the product. If a username is missing or incorrect, go to the person's profile, open the Integrations tab, and update it from there. No admin required.
Once updated, Pensero will reprocess historical data for that person so past activity is correctly attributed.
If the problem persists after validating the integrations and usernames, contact Pensero through the product chat. The team will investigate and get back to you.