Roles & Permissions
Two objects doing two different jobs. A role is a position on the org chart and settles what you can see. A profile is a permission template and settles what you may do with it.
The same five leads, resolved for six seats
3 of 5 visible- Nina KaurKestrel Health · Meridian
- Ken AdachiNorthbridge · Meridian
- Alan ReyesArdent Logistics · Meridianown
- ••••••••not resolved for this seat
- ••••••••not resolved for this seat
Product figures from the platform’s own defaults - not customer averages
How it works.
Position and template, kept apart
Where you sit in the tree governs whose records you can reach. What your profile allows governs the verbs. Several positions can share one template, which is how three regional managers get identical powers over different books of business.
Own means assigned to you
Reading is granted as own, subordinate or everything. Own is the records currently assigned to you, not the ones you originally created, and that distinction is what decides who keeps sight of a lead after it is handed on.
Sharing crosses without cascading
A rule grants one position's records to one other, for reading, writing or deleting. It does not flow down from the source and it does not flow down to the recipient, so a grant to a manager is not a grant to their whole branch.
Whom you may hand work to
Each position carries an assignment rule: yourself alone, your peers and everyone beneath, beneath only, or anybody. Named positions widen that by person; a named team widens it to the team as a destination rather than to its members one by one.
One moment in every record.
Every record passes through the same seven. Roles & Permissions is the lit one, and everything either side of it is a different page in this category.
- 01Capture
how it arrives, and from where
- 02Shape
the fields and stages it carries
- 03Find
getting back to the right ones
- 04Work
what happens against it day to day
- 05Advance
moving it towards a decision
- 06Protect
who may see it, and staying clean
- 07Report
what the floor is judged on
The specifics.
8 facts- Two objects
- A role is a position in the tree. A profile is the permission template it uses
- Entities
- Leads, deals, products, vendors, tasks, commission rules and goals
- On the form
- All seven, each with its own row of verbs on the permission profile editor
- Verbs
- Create, read, update, delete, export and import, set per entity type
- Switches
- Sixteen on the profile, all sixteen drawn on the editor, export and import among them
- Visibility
- Own, subordinate or everything, where own is assigned rather than authored
- Sharing
- One position to one other, read, write or delete, with no cascade either way
- Field level
- Granted per field group, which is the unit a profile is given view, edit or delete on
What else writes to this record.
A record is worked by more than one part of the system at once. These are the ones that put something on it, or read it back.
More in Leads & Sales CRM
11 capabilitiesThe system of record the phone writes to directly - no sync job.
Unlimited pipelines, each with its own stages, win probability, colour and temperature. Seven seeded, and every stage change writes itself onto the deal.
Create the stages your floor argues about, colour them, order them and rate them hot, warm or cold, while six fixed categories keep the reporting stable.
Ten sources seeded and sealed, your own added beside them, each with a colour and a live count, and one stamped across a whole import rather than per row.
Eleven field types, all of them on the picker, with options, defaults and a section of their own, on leads, deals, products and vendors. No cap on how many.
Columns, sorts, filters and layout save together and hand to a CRM role, so a new starter opens the same board instead of rebuilding it every morning.
Eighteen type-aware operators, a trigram search across seven columns, and a straight account of where a custom-field filter is resolved and what it costs.
Upload, map, review. Headers auto-map against the full field catalogue, imports stream so memory stays bounded, and a failed row never stops the run.
Matched on normalised email then phone, at the moment a record is written, so the duplicate is caught on the way in rather than found in a report later.
Every field change on a record with both values, beside the notes, mail, tasks and deal links against it, assembled as it happens rather than typed up later.
Calls, voicemails, emails and texts merged into one chronological history per lead, attached by the number they reached, with duration and the wrap-up code.
Tasks with assignees, reminders, comments and templates, raised by hand or by a sequence, and the only CRM object that leaves the app to find someone.
The rest of the platform.
Five more categories, all on the same record and the same bill. Each card names three of its capabilities, so you can tell from here whether it is worth opening.
Leads & Sales CRM
See roles & permissions on your own floor.
Thirty minutes, your numbers and your data. We will set roles & permissions up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included