Skip to content
KudosCRM

Launch offer 3 months free on every plan. Claim now

Roles & Permissions

Give everyone the right access — no more, no less

Role-based access control decides who can see, edit, and delete records and settings across the workspace. Set it once by role, and every teammate gets exactly the access their job needs.

Part of Team & Workloadthe stage that sets up your team — invites, roles, and the access each person gets.See the full stage

The right access for every role

An SDR, an AE, a delivery lead, and an admin don't need the same powers. Roles let you grant each the access their job needs and nothing more — without locking people out of their own work.

Sensitive actions stay protected

Deleting records, changing settings, and exporting data can be reserved for the roles you trust with them — so a stray click can't undo what the team relies on.

Onboard by role, not by checklist

Invite a new teammate, pick their role, and they inherit the right permissions instantly. No per-person setup, no 'wait, what can they see?' a week later.

How it works

Every part, explained.

1

Define what each role can do

Roles map to how your team actually works — who can view, create, edit, delete, and reach settings across the workspace.

2

Invite teammates to a role

Bring people in (one by one or in bulk) and assign the role that fits, so their access is correct from their first login.

3

Access is enforced everywhere

Permissions apply consistently across records and settings — what a role can't do simply isn't available to it.

4

Changes are on the audit log

Permission and settings changes are recorded in the audit log, so you can see who changed access and when.

Deep dive

Everything that's in the box.

Role-based access control (RBAC)

Grant access by role rather than per person, so permissions stay consistent and easy to reason about as the team grows.

Bulk team invitations

Invite multiple teammates at once and assign roles, so onboarding a team doesn't mean setting up one account at a time.

Protected destructive actions

Reserve deletes, exports, and settings changes for trusted roles, so high-impact actions aren't available to everyone.

Settings & data scope

Control reach into workspace settings and data, so admins manage configuration while reps focus on selling.

Audit-logged changes

Access and settings changes land in the audit log with who and when, so permission shifts are transparent.

Field-level permissions — rolling out

Restricting individual fields by role (beyond record- and action-level control) is on the enterprise roadmap, shown with a "Soon" pill rather than claimed as live.

KudosCRM vs. the old way

A different league.

KudosCRM
Spreadsheet / legacy CRM
How access is granted
By role, inherited the moment someone joins
Per person, hand-configured and easy to get wrong
Destructive actions
Reserved for trusted roles
Anyone can delete or export — and someone eventually does
Onboarding a teammate
Invite, pick a role, done
A checklist of toggles you hope you remembered
Tracking access changes
Recorded in the audit log
No record of who changed what permission, or when

FAQ

Frequently asked

Start free today

Ready to give your team a CRM they'll actually use?

Start free. Bring your whole team. Cancel whenever (you won't).