Security & Platform
Everyone sees just what they should.
Role-based access, per object and per person, so every team sees the records their job needs and nothing more.
Roles & permissions in practice.
Role-based access, object by object.
01
Roles that fit your org
Give sales, support, finance, and admins the access their work needs, out of the box.
02
Object by object
Set see, edit, and delete per object on each role, then override it for one person on the Growth plan.
03
A trail of what was done
The audit log on Growth records deletions, exports, role changes and settings changes, with who did each one.
One connected system
One permission model, every module.
Set access once and it holds across CRM, finance, HR, and support, instead of juggling five separate permission systems.
- One role covers every module, assigned per person.
- Sensitive finance and HR data stays with the right people.
- One permission model covers CRM, finance, HR and support.
The other feature in Security & Platform.
All five products on every plan, on the same connected data.
Questions, answered.
Can I control access down to the field?
No, and we would rather be blunt about it. Access is set per object — deals, invoices, tickets, people — not per field, so a role either sees a record or it does not. On the Growth plan you can override any object for one person, which is as fine-grained as it gets today.
Is there an audit trail?
Yes, for changes. The audit log on Growth records who deleted records, who exported them, who changed a role, a setting or the plan, with a timestamp and an IP. Reads are not logged, so it will not tell you who opened a record.
