Granular permissions
without IT tickets.
Custom roles, a full permission catalogue, per-assignment constraints (e.g. approve expenses up to £500), team-scoped budgets, multi-departmental access. RBAC powerful enough for enterprise, simple enough for a 5-person team.
The access model your auditor will love.
Custom roles
Start with Finance Admin, Sales Manager, Marketing Specialist, Employee. Or build your own from the permission catalogue.
Permission catalogue
Every action in Clkly maps to a named permission. View, edit, approve, delete, export - tick what each role can do.
Constraints per assignment
Approve expenses, but only up to £500. View deals, but only your own. Edit invoices, but not after they are sent.
Multi-department access
A finance lead also covers ops? Assign multiple roles. Scoped by department, summed at the user level.
Team-scoped budgets
Sales team owns one budget, Marketing another. Per-user spend cap nested inside the team cap. Live tracking.
Audit trail
Every privileged action logged - who, what, when. Exportable for SOC2 / ISO 27001 / your annual review.
No more spreadsheet of who-can-see-what.
Most SMB CRMs give you admin / member / read-only and call it RBAC. Clkly gives you a real permission catalogue, real constraints, real audit. The kind of thing you need before your first enterprise customer asks.
- Per-record scopingRestrict deals, contacts and invoices to the owner's team by default.
- Approval routingBills over £1k? Auto-route to a Finance Admin. Expenses over £500? Manager approval.
- Safe defaultsNew hires land in 'Employee' - read most, write little. Promote when ready.
Permissions FAQs
What do permissions control?
Permissions decide who can see and do what across the CRM, from records to settings.
- Set roles for different team members
- Restrict sensitive data to who needs it
- Control who can edit, delete or export
Clkly gives you role-based access, so the right people have the right reach and no more.
Related: Spaces · Compliance
Can I set role-based access?
Yes - define roles once and assign them, instead of configuring each person by hand.
- Reusable roles for common job types
- Scope access by Space or team
- Change a role and it applies to everyone in it
Role-based access keeps permissions consistent as the team grows.
Related: People + HR
How do permissions support security and compliance?
Tight access control plus audit logging shows who did what, which auditors expect to see.
- Least-privilege access by default
- Audit trail of changes
- Evidence for security certifications
Good permissions are the backbone of both day-to-day security and certification readiness.
Related: Compliance
Open up the right doors. Keep the rest shut.
Default roles on every plan. Custom roles + constraints on Pro.