Help centre / Vendra CRM

Roles & permissions

How role-based access works in Vendra One: the twenty built-in roles, the permission matrix, and why you cannot assign a role above your own.

Access is controlled by roles. A role is a named set of permissions, and every permission is a module plus an action — for example deals.delete or invoices.export.

The built-in roles

Twenty roles ship with every workspace, from Super Admin down to Viewer, covering the usual sales, finance, support and technical functions. They are ordinary records, not hard-coded: rename them, change what they can do, or add your own.

The permission matrix

Each role has a grid of modules against six actions: view, create, edit, delete, export and manage. Ticking a whole row grants everything for that module. The matrix is the entire truth about a role — there are no hidden extras.

Levels stop privilege escalation

Every role carries a level. You cannot create, edit or assign a role at or above your own level, which means a Sales Manager cannot quietly promote themselves to Admin, or hand a colleague more access than they hold themselves.

A role cannot be deleted while anyone still holds it. Move those people first — deleting would otherwise leave them with no permissions and no obvious explanation.

Teams are separate

Roles decide what someone may do. Teams decide what work is theirs. A ticket assigned to the Support team belongs to everyone on it until one person picks it up, which is why both exist.

Keep reading

Set up your workspace Import contacts & leads How the 7-day trial works

Try it on your own pipeline

Seven days free, no card required. Import a list and make your first call this afternoon.

Start free trial