People, Org Tree & Form Types
How to navigate your organisation structure, view rep responsibilities, and manage the form types used in field execution. About 6 minutes.
The People section of KeyOne gives you visibility into who is responsible for what — people, territories, categories, and form types — and lets administrators set manager relationships and responsibilities.
Field rep roster
Route: /app/people/field-reps
The roster shows every field rep in your tenant as a card: their name, their rep code, whether they are active, and how many outlets are assigned to them. Above the cards, a summary strip totals the active reps, the outlets assigned across the team, and the average outlets per rep.
There is no territory column and no open-task count — the rep record carries neither, and the roster shows only what it actually holds. Click any card to open that rep’s detail page.
/app/people itself is the organisation roster (people and their roles),
not the field reps; the two are separate lists.
Rep Detail
Route: /app/people/:repId
The Rep Detail page is a single page — there are no tabs.
It shows what the server actually sends for a rep, and nothing it does not:
- Name and Status (active or inactive)
- Outlets assigned — how many outlets are on this rep’s roster
- Open decisions — the work currently sitting with them
- Recent visits — their latest visit records
What used to be here, and why it is gone. This page once carried four KPI tiles (Calls Per Day, Productive Calls, ECO Coverage, Beat Plan), a Performance Score ring with a target marker, and a nine-field settings panel — plus Beat Plan and Responsibilities tabs. The rep endpoint has never sent the fields behind any of it, so every one of them was permanently blank on every rep in every tenant. They were removed rather than left rendering empty: a blank score ring beside a target marker is not neutral, it reads as “this person has not been measured yet”, which is a claim about them.
If you need territory, category or channel ownership per rep, that is a genuine gap rather than a hidden screen — say so and it can be built against a real endpoint.
Org Tree
Route: /app/people?tab=org-tree — the org tree is a tab on the People page, not a page of its own. (/app/people/org-tree redirects there.)
The Org Tree shows your field organisation as a hierarchy — managers with their direct reports, collapsible by node.
Reading the tree
- Each node shows a person’s name, role, and territory.
- Click a node to expand or collapse its subtree.
- Use the search box at the top to jump to any person by name — the tree highlights the matching node.
- Nodes with no manager are shown at the root level.
Setting a manager relationship (admin)
Administrators and organisation owners can set who reports to whom:
- Find the person you want to assign a manager to.
- Click the Set manager icon on their node.
- Choose the manager from the picker (any member can be a manager).
- Confirm — the tree re-renders with the new relationship.
A person cannot be their own manager — the API rejects it with a 400 and the message “a person cannot report to themselves”. A circular relationship (A → B → A) is rejected the same way.
Form Types
Route: /app/people/form-types
Form Types are the templates for structured data capture in the field. They define what information a rep collects when completing a specific type of visit activity.
The three seeded form types
| Form type | Purpose | Fields captured |
|---|---|---|
| Dormant outlet check | Establish whether an outlet that stopped ordering is still trading | What you found, storefront photo, who you spoke to, contact number, when they expect to reorder, what they told you |
| Out of stock — reason | Record why a line is not on the shelf | Product that is out, shelf confirmed empty, why it is out, stock in the back room, date of last delivery, shelf photo, notes |
| Promotion execution check | Confirm promotional material actually reached the store | Which promotion, material is up, where it is displayed, photo of the display, if not up why not, notes |
A shelf audit and an order pad are not form types. They are dedicated capture surfaces in KeyLink with their own tables and their own screens.
Creating a custom form type
- Click + New Form Type on the Form Types page.
- Give it a name and optionally a category filter (so it only appears for relevant visit types).
- Define the fields — label, field type (text, number, dropdown, date), and whether required.
- Save — the form type becomes available immediately in KeyLink for field reps.
No form type can be deleted — the API exposes create, read and update and no delete, for seeded and custom types alike. Deactivate one instead: it stops appearing in KeyLink while the captures already filed against it keep their meaning. Creating, reading and editing form types is admin and internal only.
Where to go next
- KeyLink for Field Reps — how reps use form types on visits
- Org management in Settings — invitations and member roles
- Glossary — territory, call plan, beat plan