Roles and RBAC

How access works

Snowmass controls what each person can do through roles assigned within your organization. A member can hold more than one role. Every screen and action is checked against the member's roles, so people only see and touch what their job needs.

The built-in roles

• Admin — full control: organization settings, billing, people and roles, and all operations. Only admins can change the settings described in this section.
• Dispatcher — runs storms: opens events, monitors the live ops dashboard and map, reserves stops, and messages the fleet. No access to billing or org settings.
• Operator — runs a machine in the field: joins a run, claims and completes stops on the tablet, logs materials and incidents. Can optionally be limited to specific locations (see the next article).
• Customer service — handles support tickets and customer communication; sees customer and event data without dispatch or admin powers.
• Viewer — read-only. Can see operations and reports but change nothing. Good for stakeholders who need visibility without a hand on the controls.
• Customer — the property-owner portal role: sees only their own properties, events, service history, and notifications. Strictly scoped to their own records.

Assigning roles

An admin assigns roles per member. Start people at the least access their job requires and add roles as needed — a dispatcher who also runs a machine gets both dispatcher and operator, for instance.

A note on the model

Authorization is by role type. There's no separate per-permission checklist to maintain — the six roles above (plus any custom roles your org defines) are the unit of access, which keeps administration simple.