Users & Permissions

Roles, page-level permissions, and custom overrides

Users & Permissions

Beam uses a role-based access control system to manage what each user can see and do within your organization. Roles define a baseline set of permissions, and administrators can further customize access on a per-user basis.

Roles

Every user in Beam is assigned one of three roles. Each role builds upon the previous one with increasing access levels.

RoleDescription
UserStandard access. Can view and interact with items, orders, and other enabled modules based on their permissions. Suitable for warehouse floor staff and day-to-day operators.
SuperuserExtended access. Includes all User permissions plus the ability to perform advanced operations such as bulk edits, exports, and extended reporting. Ideal for team leads and supervisors.
AdminFull access. Includes all Superuser permissions plus access to the Settings page, user management, and all configuration options. Reserved for organization administrators.

Page-Level Permissions

Permissions in Beam are organized by feature area. For each feature, two permission levels can be configured:

  • Read the user can view the data in this feature (e.g., see items, view orders, browse reports).
  • Write the user can create, edit, and delete data in this feature (e.g., add items, modify orders, create tasks).
📝
Write permission always includes read permission. If a user can edit items, they can also view them.

Permission Configuration per Role

Each role comes with a default set of permissions that determines what users in that role can access. Administrators can view and adjust the default permissions for each role in the Settings page. Changes to role permissions affect all users assigned to that role.

Custom Permission Overrides

In addition to role-level permissions, Beam supports per-user fine-grained permission overrides. This allows administrators to grant or restrict specific permissions for individual users without changing their role.

For example, you could give a standard User read access to the Reports module, or restrict a Superuser from accessing a specific action type. Custom overrides take precedence over the default role permissions.

⚠️
Use custom permission overrides sparingly. Relying too heavily on per-user overrides can make your permission structure difficult to manage. When possible, adjust role-level permissions instead.
💡
Regularly review your user list and permissions to ensure that access levels are still appropriate, especially after team changes or when new modules are enabled.