Skip to main content

User Roles and Permissions

Roles

Organization Admin · Event Coordinator · Treasurer · Board Member · Document Manager · Family Lead · Family Worker · Guest Worker

StandShare uses a role-based access control (RBAC) system. Each user is assigned one or more roles, and each role grants a specific set of granular permissions. This page is a reference — for a conceptual explanation of how the system works, see Understanding Roles and Permissions.


User types

StandShare has three structural user types. These are not roles — they determine the scope of access before any role is considered.

User TypeDescriptionHow access is granted
Platform AdminStandShare staff who manage the platform itselfHold the Admin role, which passes all permission checks
Org MemberAnyone belonging to an organization (coordinators, families, etc.)Assigned one or more roles through the Admin > Users interface
Guest WorkerNon-members who participate in eventsAssigned the Guest Worker role

Built-in roles

StandShare ships with 14 built-in roles across three groups. Admin and Venue Admin are system roles and cannot be edited or deleted. All other built-in roles can be modified to fit your organization's needs.

NPO organization roles

RoleSystem RoleDescriptionKey Permissions
AdminYesFull system access — bypasses all permission checks. Cannot be modified or deleted.All permissions (wildcard *)
Organization AdminNoFull tenant-scoped access to all org features.All NPO permissions across every category
Event CoordinatorNoManages events and worker assignments through full settlement.Create/edit events, assign/remove workers, enter commissions, record attendance, settle events (not reversal), manage venues and groups, manage partnerships
TreasurerNoManages financial records and approvals.View all family accounts and transactions, manually adjust transactions, approve/deny/process scholarship requests, view fund balances and transactions, view/create ledger entries, view billing
Board MemberNoRead-only oversight of all financial and event activity.View all family accounts and transactions, view events and event reports, view fund balances and transactions, view document compliance, view ledger, view billing
Document ManagerNoManages contracts and compliance documentation.Upload documents for any family, view all documents, manage document templates, distribute for signature, view compliance reports
Family LeadNoPrimary family account holder.View and edit own family account, view own transactions, submit own scholarship requests, upload and view own documents
Family WorkerNoWorks events with minimal access.View events only
Guest WorkerNoGuest with limited portal access.View own assigned events, view own assignment details and earnings, view library content, view member directory, submit feedback

Venue roles

RoleSystem RoleDescriptionKey Permissions
Venue AdminYesFull venue portal management. Cannot be edited or deleted.View/manage venue profile, view/manage venue users, view/manage venue billing
Venue CoordinatorNoDay-to-day venue operations; no billing or user management.View venue profile, view venues, manage venues, view venue users
Gate AttendantNoScanner-only access for check-in.View venue profile, view venues

Operator roles

RoleSystem RoleDescriptionKey Permissions
Operator AdminNoFull operator access — venue portal, operations, event reporting, groups, and API keys.Manage venue profile, manage venue users/billing, view operations dashboard and system health, export metrics, view event reports, manage groups, manage API tokens
Operator CoordinatorNoRead-only operator access.View venue profile, view venue users/billing, view operations dashboard, view event reports, view groups

Permission categories

Permissions are organized into the following categories:

CategoryCode PrefixWhat it covers
Family Account Managementfamily_account.*Viewing and editing family accounts, transactions, and exports
Event Managementevent_management.*Creating, editing, and settling events; assigning workers; managing rosters
Scholarship Requestsscholarship_requests.*Submitting, viewing, approving, denying, and processing scholarship payments
Fund Managementfund_management.*Viewing fund balances, configuring rates, toggling deductions, exporting reports
Document Managementdocument_management.*Uploading, viewing, and managing documents and templates; distributing for signature
Communicationcommunication.*Sending messages, managing notification templates, viewing communication history
System Administrationsystem_admin.*Creating and editing roles, assigning roles, configuring security, managing settings, viewing audit logs
Admin Paneladmin_panel.*Viewing user directory, managing users, sending invitations, revoking sessions
Librarylibrary.*Viewing and managing published content, viewing analytics, managing content categories
Announcementsannouncements.*Creating, editing, pinning, and deleting announcements
Directorydirectory.*Viewing the member directory
Ledgerledger.*Viewing and creating ledger entries and fund transfers; voiding entries
Billingbilling:*Viewing and managing billing and subscription information
Operationsoperations.*Viewing the operational dashboard, system health indicators, and exporting metrics
Collaborationcollaboration.*Managing partnerships, inviting partners, managing cross-org worker assignments, settling payouts
Guestguest.*Viewing own events and own assignment details (Guest Worker portal access)
Venue Profilevenue_profile.*Viewing and managing venue profile and settings
Venue Usersvenue_users.*Viewing and managing venue staff
Venue Billingvenue_billing.*Viewing and managing venue subscription
API Tokensapi_tokens.*Creating, viewing, and revoking API keys
Feedbackfeedback.*Submitting and managing feedback
FAQfaq.*Creating and editing FAQ entries
Groupsgroups.*Viewing and managing operator groups

Permission inheritance rule

Within a category, holding a view_all permission automatically satisfies a view_own check. For example, a user with family_account.view_all does not also need family_account.view_own — the broader permission covers the narrower one.

This applies only to view permissions. Edit permissions (edit_all and edit_own) do not chain in this way.


Assigning roles to users

  1. Navigate to Admin > Users.
  2. Click on the user you want to modify.
  3. Click Manage Roles (step-up authentication required).
  4. Select or deselect roles as needed.
  5. Click Save.

A single user can hold multiple roles simultaneously. Their effective permissions are the union of all roles they hold.

For full instructions on inviting users, managing the user list, and creating custom roles, see Manage Users and Roles.


System role immutability

Only Admin and Venue Admin have system-role protection. Attempting to edit or delete them returns an error. All other built-in roles — including Organization Admin, Event Coordinator, and Treasurer — are editable and can be deleted if your organization does not need them.


Permission cache

Permissions are cached per user for 5 minutes. When an admin changes a user's roles:

  • The individual user's permission cache is cleared immediately.
  • When a role's permissions are edited, all user permission caches are cleared at once.
  • Either way, the updated permissions take effect within the 5-minute window on the user's next request.

Next Steps