Managers see their team. Reps see their work. You decide the rest.
Build an org chart from reporting lines, departments and designations. Each role carries a data scope, own, team, or all, separate from its permissions. Customers create their own roles, and a custom role works everywhere a built-in one does.
- Org hierarchy, org chart, departments and designations
- Each role carries a data scope: own, team, or all
- 328 individual permissions across 53 modules
- Five system roles (Owner, Admin, Manager, Sales, Lead Gen), plus custom roles you create
- Isolation between customers is enforced in the database, not only in application code
- A request that cannot resolve which business it is for is refused, never widened to everything
Roles and scope
Permissions and scope, set separately.
A role decides what someone can do; its data scope decides whose records they see: their own, their team's, or everyone's. Nothing in the product checks for a role name, so a custom role works everywhere a built-in one does.
Several businesses
A hard fence between businesses.
If you run several workspaces, granted access is a hard fence, even for an admin. Being an admin decides how much of a business you can see, never which businesses. A consolidated view across workspaces is a separate grant, off by default for everyone.
16: Org Hierarchy & Scope