Roles and visibility
Everyone sees the organization's numbers. Individual detail is seen only by the person and by the managers and admins responsible for their team. Nobody is ranked, and nobody gets a score.
The three roles
- Developer: sees the organization's numbers, their own team, and their own profile.
- Manager: also sees their team and the teams under it, with each member's numbers, and gets their own team's digest by email.
- Admin: sees everything, and runs the workspace: Members, Connections and Admin.
Admins set roles on Members. A member is linked to their person, the human behind their Jira and GitHub accounts, which is how we know which profile is theirs and which team they're on. Invitations match people by email; you can also pick the person by hand. Nobody can change their own role, so a workspace always keeps an admin.
Who sees what
| What | Developer | Manager | Admin |
|---|---|---|---|
| Org overview, initiatives, AI leverage (team totals and anonymous groups) | Yes | Yes | Yes |
| Team dashboards | Their own team | Their team and the teams under it | All teams |
| Team member lists and per-person stats | No | Their teams | All teams |
| A person's profile | Their own | Their own, and people on their teams | Everyone |
| “Needs a conversation” | No | Their teams | All teams |
| Weekly digests on the Digests page | Their team's | Their teams' | All teams' |
| Weekly digest by email | No | Their team's | Every team's (each can be turned off) |
| Members, Connections, Admin | No | No | Yes |
The digest itself never names individuals: it's about the team's work. The same table is on our Who sees what page.
“Needs a conversation”
Team dashboards can mark a person as worth a conversation. It's designed to start a conversation, never to end one, so the rule is strict:
- In each of the team's last two completed sprints (or the last two fortnights, for a team that doesn't run sprints), they were below the team's middle value on both priority work finished and reviews given.
- And their priority work finished isn't trending up.
Two separate signals, two periods in a row, and no improvement: one slow sprint, a vacation or a big investigation won't do it on its own. Managers aren't included, either as candidates or in the team's middle value.
Only the person's managers and admins see the mark, and it always comes with the numbers behind it, period by period, next to the team's. The person sees all the same numbers on their own profile, but not the mark. There's often a good reason: on-call, mentoring, work outside Jira. The point is to ask.
What we don't do
- No rankings or leaderboards, and no single score per person.
- AI usage is context beside delivery, never a target or a productivity measure.
- Truly Shipped staff don't browse workspace data. We open it only when you ask for support or to fix an incident.
Stuck? Write to chris@trulyshipped.com and we'll help.
Next: Use it from your AI assistant →