Skip to content
Nexxus

Access Control

Nexxus uses role-based access control (RBAC) to determine which parts of the system a user can access and which actions they can perform.

Permissions are assigned to roles rather than directly to individual users. When a user is assigned a role, they inherit all permissions associated with that role.

Multiple Roles

Section titled “Multiple Roles”

A user can have multiple roles.

When multiple roles are assigned, Nexxus combines their permissions. This means a user receives the permissions from every role assigned to their account.

For example, if one role allows a user to create events and another role allows them to manage clients, assigning both roles gives the user access to both capabilities.

Feature Access

Section titled “Feature Access”

Permissions control both navigation and actions.

A user may not see a sidebar link if they do not have permission to access that feature. Permissions can also control specific actions within a page, such as creating, editing, deleting, approving, or sending information.

This allows Nexxus to provide different levels of access without requiring separate versions of the application.

Permission-Based Features

Section titled “Permission-Based Features”

Some features depend on specific permissions.

For example:

  • Approve Talents also provides access to the talent approval workflow and its internal notes.
  • Direct Message Anyone allows a user to initiate direct conversations.
  • Create Group Message allows a user to create group conversations.
  • Send Call Sheets allows a user to send call sheets through messages.
  • View All Calendar Items allows a user to view calendars beyond their own relevant schedules.
  • Filter Calendar by User allows a user to filter schedules by specific users.

This permission-based approach keeps access flexible and allows Nexxus to adapt to different organizational workflows.

Section titled “Related”