People, Roles & Access
The reporting line is not decoration. It is the permission model.
Build the organisation once — departments, reporting lines, roles — and visibility follows it. A manager sees their own tree, and the totals on their dashboard are their tree's totals, because an aggregate leaks a record just as effectively as a list does.
Organization
Updated just now
Meera Iyer
Director
Rohit Kumar
Sales manager
Sneha Nair
Executive
Tom Joseph
Executive
Aisha Khan
Marketing lead
Vikram Das
Executive
Hire to access
How a new person gets exactly the access they should have.
Access is derived from the organisation, then adjusted per person. Never the other way round.
0107Your team
One person, or a spreadsheet of them
Add someone directly, or import an Excel or CSV file of the whole team.
Happens on /organization in the product
- Import validates the file and the existing database together as one graph, in three passes, then shows you a preview.
- The commit is all-or-nothing. A half-imported org chart with dangling reporting lines is worse than a failed import.
In the product
What you get, and why it is there.
Records are owned
Ownership is enforced across every module, so 'my leads' means the same thing everywhere in the product.
Resources are allocated, not assumed
Nothing is shared by default. A WhatsApp number is private to its owner until it is explicitly allocated or shared.
Multiple accounts, cleanly separated
Sign into more than one workspace the way you do with mail, with per-tab isolation so two tabs never bleed data into each other.
A permission grid, not a checkbox list
Roles are edited as a module-by-action matrix, which is the shape the model actually has.
Departments with real meaning
Departments drive both the chart and the routing rules, so distribution follows the organisation rather than a second list of names.
Protected ownership
The platform owner account is protected in code, not by convention, so it cannot be locked out or deleted by an administrative accident.
Where each step actually happens
These are real screens in the product, not stages in a diagram. You can be looking at every one of them on day one.
See the whole platform mapOnboard
One person, or a spreadsheet of them
Structure
Departments and reporting lines
Role
A role sets the defaults
Adjust
Then grant or revoke for one person
Audit
Who did what, and when
Keep going
What connects to this
Ready when you are
See People running on your own process.
Bring a real example — an enquiry that got lost, a quote that took three days, a campaign nobody could measure. We will walk it through the actual product.