User Roles and Permissions

Go to Staff in the sidebar (requires user_module permissions).

1. Click Add Staff and enter name, email, phone, and password.
2. Assign a Role — permissions come from the role, not individual checkboxes on the user form.
3. Staff sign in at the same /login URL as admin using their email and password.
4. Staff can update their password from their profile page.
5. Use Import on the staff list to bulk-add users from Excel (see Import & Export docs).

Go to Staff → Roles (admin or users with role_module access).

1. Click Add Role, enter a role name and description.
2. Enable module permissions: Contact, Role, User, Lead, Lead Kanban, Lead Pipelines, Product, Office, Expense — each with create / read / update / delete as needed.
3. Save the role, then assign it when creating or editing staff.
4. Default roles ship with the CRM; duplicate them before customizing so you keep a baseline.

DevPremier CRM uses module-level RBAC. Each role stores permissions per module (e.g. lead_module, contact_module).

• Sidebar menu items appear only when the signed-in user’s role grants access.
• List, create, edit, and delete actions are enforced in controllers and policies.
• Admin role (typically role_id = 1) has full access including Office settings and both lead Kanban modules by default.
• If a staff member cannot see a menu, check their role permissions before changing user records.
• Lead list/create/edit/delete still uses lead_module; Kanban and pipeline settings use separate modules (see below).

Two additional modules control the v3.0 lead pipeline features. Enable them under Staff → Roles when editing a role.

• lead_kanban_module — intended for Leads → Kanban. Planned mapping: Read = view board, Update = move cards and stage updates.
• lead_pipelines_module — intended for Leads → Pipeline. Planned mapping: Read = view settings, Create / update / delete = pipeline and stage CRUD.
• delete-lead remains the required permission for delete actions (including any future bulk delete workflow).

Gates map to these actions: view-lead-kanban, update-lead-kanban, view-lead-pipelines, create-lead-pipelines, update-lead-pipelines, delete-lead-pipelines.

Admin (role_id = 1) receives both modules enabled automatically. Sales or support roles need explicit read (and update, if they should move cards or manage pipelines).

Call notes, SMS, and lead CRUD still follow existing lead_module permissions.