Roles and permissions

Purpose: a stable reference for names your organization uses on stage and in the app. Exact role labels in the product may vary; map them to these ideas when you train staff.

Who can use this

Everyone skimming for definitions; admins use it when assigning access.

Core ideas

Idea	What it means for users
Facility	A school site or program unit. Your account is tied to one or more facilities.
Role	What you may do (view, edit, approve loans, manage users).
Module	Major area: drama inventory, music, billing, and so on—your contract may not include all modules.

Typical role patterns (examples)

These names are illustrative; your Users screen shows the real list.

Viewer / read-only — search and open items; no edits.
Staff — day-to-day edits, checkout, photos.
Site admin — users and settings for one facility.
Org admin — cross-site or district settings, sometimes billing.

What happens next

Admins: user management to apply changes.
Admins: permissions for policy tips.

Common problems

“This page lists five roles but we only use three” — hide unused roles in training materials; only assign what you need.

Terms and labels