> ## Documentation Index
> Fetch the complete documentation index at: https://learn.nexudus.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Roles and permissions

> Understand how user roles control access to features and data in the Nexudus dashboard.

## 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](https://learn.nexudus.com/platform/settings/users-and-roles) for step-by-step instructions.

## How it works

Access in the dashboard is built from three parts:

1. **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**.
2. **Roles** — named groups of permissions. A role defines which records its members can access or manage.
3. **Users** — staff accounts that are assigned one or more roles, plus the locations they can work in.

> [!NOTE]
>
> 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:

1. **A staff account** — the person exists as a user in **Settings → Users** with a working password (or SSO).
2. **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.
3. **Location access** — at least one location selected on the user's **Access** tab. A user with roles but no locations has nowhere to work.

The **Dashboard** template provides the base permissions every role needs: access to the dashboard itself plus read/list access to core reference data such as businesses, users, languages, currencies, time zones, and business settings.

> [!WARNING]
>
> A restricted administrator with no roles — and without the full unrestricted toggle — can sign in but can't do anything in the dashboard.

## 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.

> [!WARNING]
>
> Limit the number of full unrestricted administrators. This access covers every location, setting, and record in your account.

## Role templates

When you create a role, you start from a set of templates that tick the relevant permissions for you:

| Template | Intended for |
| - | - |
| Dashboard | Basic access — required for the role to appear in the dashboard at all |
| Read only | Viewing data without making changes |
| Reception | Front desk: check-ins, bookings, visitor logs |
| Finance | Invoices, payments, and billing records |
| Inventory management | Stock and inventory records |
| Web developer | Website and portal configuration |
| Community manager | Content, events, and community features |
| Sales | CRM boards, opportunities, and proposals |
| NexDelivery | Delivery scheduling features |
| NexBoard | Board-related features |

You can combine several templates on one role — the permissions add together — and then adjust individual permissions afterwards.

> [!NOTE]
>
> 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](https://learn.nexudus.com/platform/settings/role-permissions-list.md).

## Where roles are managed

* **Settings → Users** — create staff accounts and assign their roles and locations.
* **Settings → Roles** — create, copy, and edit roles.

Roles are available across your whole network: a role you create in one location can be assigned to users in any location.

## Best practices

> [!TIP]
>
> Follow the principle of least privilege — give each person only the access they need to do their job.

* **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

> [card] [Users and roles](https://learn.nexudus.com/platform/settings/users-and-roles)
>
> Create users, build permission groups, manage 2FA and account owners.

> [card] [Creating administrators](https://learn.nexudus.com/platform/settings/creating-administrators.md)
>
> Add full or restricted administrator accounts.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.