People, identities and teams

Every number is built from people and the teams they're on. Truly Shipped matches people across your tools on its own; a few minutes of review after each sync keeps the numbers right.

People and identities

An identity is one account in one tool: a Jira user, a GitHub login, a Claude login. A person is the human behind them. We join identities into people by email. When a tool gives us no email, which is common for GitHub, or the emails differ, the same human can show up as two people until you merge them.

You manage people in Admin (under your name, in the Workspace section). It opens on People.

Reviewing people

Anyone new from a sync starts as “needs review”, and the People list opens filtered to them. Each one says why they need a look:

• May be the same person as …: their name, email or GitHub login looks like someone already here. Usually a duplicate to merge.
• No email, so they couldn't be matched across tools: typical for a GitHub login.
• Found only in GitHub (or Jira, or Claude): they may have accounts elsewhere under another name.
• Not on a team: they won't count toward any team until they're on one.

Fix what needs fixing with the actions below, then tick them and choose Actions → Mark as reviewed. Merging and reassigning mark people reviewed on their own.

Merging duplicates

Tick the duplicate, choose Actions → Merge into person, and pick the person to keep. Their identities move over, any blank email, level or team is filled in from the duplicate, and the duplicate is removed. Their past work moves with them, so every chart updates at the next overnight recalculation.

Moving or splitting one identity

If one account landed on the wrong person, open Identities, tick it, and use Reassign to person. If two humans were joined by mistake, Split into new person gives that account a person of its own. Identities come only from your tools, so they can't be created or deleted by hand.

Fields on a person

Leavers

When someone leaves, set their Last day and leave their team as it was. They keep counting in the weeks they worked, so past numbers don't shift, and drop out of every week after. A week counts only if their last day was after its Monday. To stop them signing in, deactivate them on Members as well.

Teams

Create teams in Admin → Teams. A team can have a parent: a manager of the parent sees the teams under it too. Put people on teams from their page in Admin → People. Team dashboards and digests fill in after the next overnight recalculation.

When someone changes teams, update their team. Their past work moves with them, so their old team's history changes too. If that matters for a report, note the date.

Priorities

Priority alignment needs to know which work was a priority. Add this quarter's initiatives in Admin → Initiatives, then open Admin → Epics and set each epic's initiative. You can also set an epic's team when the Jira project doesn't say. Tags stay put when Jira syncs.