Overview
The Nexudus dashboard uses a role-based access system to control what each team member can see and do. This page explains how roles and permissions work; see Users and roles for step-by-step instructions.How it works
Access in the dashboard is built from three parts:- Permissions — the smallest unit of access. A permission combines a record type (for example, bookings or invoices) with an action: List, Read, Edit, Create, or Delete.
- Roles — named groups of permissions. A role defines which records its members can access or manage.
- Users — staff accounts that are assigned one or more roles, plus the locations they can work in.
A user can have multiple roles. Permissions are additive — if any assigned role grants a permission, the user has it.
Minimum requirements for dashboard access
For a user to sign in and see anything in the dashboard, three things must be in place:- A staff account — the person exists as a user in Settings → Users with a working password (or SSO).
- At least one role with base access — the role must include the Dashboard template (or equivalent base permissions). Without it, the user has no access to the dashboard shell or its reference data, even if other roles grant record permissions.
- Location access — at least one location selected on the user’s Access tab. A user with roles but no locations has nowhere to work.
Full access versus restricted access
Every staff account is either a full unrestricted administrator (complete access to everything) or a restricted administrator whose access is limited to the permissions in one or more roles.Role templates
When you create a role, you start from a set of templates that tick the relevant permissions for you:
You can combine several templates on one role — the permissions add together — and then adjust individual permissions afterwards.
A user’s combined roles must include the Dashboard template (or equivalent base permissions) for them to see anything in the dashboard.
Permissions work per record type
Permissions apply to individual record types, so a role can grant broad access to one area while leaving another untouched. For example, a reception role might allow staff to list and edit bookings but not delete them, with no access to invoices at all. For the complete reference of every available permission, see Role permissions list.Where roles are managed
- Settings → Users — create staff accounts and assign their roles and locations.
- Settings → Roles — create, copy, and edit roles.
Best practices
- Build one role per job function (reception, finance, and so on) rather than granting everyone administrator access.
- Review access regularly when people change roles or leave your team.
- Use location restrictions on each user’s Access tab to keep staff within the locations they work in.
- Test as the user by signing in with a test account to confirm the right features are visible.
Related pages
Users and roles
Create users, build permission groups, manage 2FA and account owners.
Creating administrators
Add full or restricted administrator accounts.