People holds one record per person: how to reach them, their emergency contact, their accounts on other systems, and their employment record.
Everyone maintains their own:
Phone numbers have a country picker and are stored in international format, so they work wherever they are used. If you paste a number that already starts with +, that wins over the picker — otherwise a French number typed while the picker said United Kingdom would be stored as a different, valid-looking, wrong number.
Where an address lookup is configured, start typing an address and pick a suggestion to fill the fields below. It is only a shortcut: every field stays directly editable, because plenty of real addresses are not in any index.
Job title, start date, end date and employment notes are maintained by HR. They appear on your profile but are read-only and marked as such.
This is not tidiness. Leave accrual and tenure bands are calculated from your start date, so a self-editable start date would be a way to grant yourself more holiday.
HR admins get a list of everyone down the left. It includes people who have no profile yet, flagged as such — so a new joiner can be selected and their record started without waiting for them to fill anything in.
Selecting somebody shows their profile, compensation and documents.
Archiving somebody on Team takes away their access. It does not take away their record. They move to an Archived section at the bottom of the roster, closed by default; typing in Filter by name finds them without opening it.
Open an archived person to update their profile, record compensation, or add documents — a final payslip or a leaving letter, say. Documents can be added even if they never filled in a profile.
Archived people cannot be ticked for a details request and have no Request missing details button: they cannot sign in to answer one.
Your own profile shows a dial and a percentage, with the fields still missing listed beside it. Click a field name to go straight to it.
The dial has one segment per field: green when it is filled in, pale when it is missing. Hover a segment to see which field it is. Your own dial counts only the fields that are yours to fill in, so it can reach 100%.
HR admins see the same dial against every name in the roster, with the percentage and the date the person was last asked.
Open somebody to see what is missing, split two ways:
Under that is when they were last asked, who asked, and how many times. The button follows from that:
| State | Button |
|---|---|
| Never asked | Request missing details |
| Asked before, still missing something | Resend request |
| Nothing left that they can fill in | No button — there is nothing to ask for |
To ask several people at once, tick them in the roster and choose Request details from N people. Select everyone with details missing ticks the whole list in one go; if you have filtered the list by name, it ticks only the people shown. People with nothing left to fill in cannot be ticked.
Afterwards you are told how many emails went, how many people turned out to need nothing, and who could not be emailed and why. Anybody whose email failed stays ticked so you can try again.
Each person gets one short email asking them to complete their profile, with a Complete my profile button. It does not list what is missing — their profile shows that when they arrive. They sign in as usual — the link is not a way in by itself.
What this does not do: it does not send reminders by itself, and it does not stop anybody tracking time while their profile is incomplete. A request goes out only when an HR admin sends one.
The assistant can report on profile details: job title, start and end dates, contact details, emergency contact, linked accounts, how complete each profile is, and — for HR admins — which systems each person is recorded as having access to.
The same rules apply as on the page. An HR admin can ask about anybody, including people who have been archived. Anybody else gets their own record only.
This works in the in-app assistant, in Slack, and from Claude through the connector when you connected by signing in. A connection made with an organization API key cannot read profiles at all: a key is not a person, so there is nobody whose access it could be using.
Compensation and documents are never returned to the assistant.
GET /api/v1/people and GET /api/v1/people/{id} return the same details as JSON. See the API reference at /developers for the fields.
Updated 2026-10-01. Still stuck? Contact support or return to the Help Center.