Audience: Call Takers, Dispatchers, Supervisors, Administrators
Last Updated: 03/12/2026

After reading this guide, you will understand how Roles & Permissions work in the Prepared platform and how they control what users can view, access, and manage within the system.

Prepared now uses a Role-Based Access Control (RBAC) system to manage user access.

Previously, users were assigned a single fixed role such as:

• Administrator

• Supervisor

• Dispatcher

• Call Taker

These roles had predefined permissions that could not be modified.

With RBAC, access is more flexible.

Now:

• Users can have one or multiple roles

• Each role contains a set of permissions

• Agencies can create custom roles that match their operational structure

This allows dispatch centers to control exactly what each user can access and do within the platform.

You can find this feature under:

Supervisor Settings → Roles & Permissions

Prepared includes several system roles that agencies can assign to users.

These roles provide default permissions for common operational positions.

Some legacy roles have been retired as part of the RBAC update.

Permissions determine what a user can see or do in the platform.

Permissions are grouped into five categories.

Incident permissions control access to calls and chatrooms.

Examples include:

• Viewing incidents

• Creating incidents

• Sending messages

• Requesting media or livestreams

• Viewing flagged incidents

Examples of incident permissions:

Media permissions control how users interact with media files.

Analytics permissions control access to reporting features.

Settings permissions control who can configure the platform.

Examples include:

• Agency settings

• User management

• Workflow settings

• Canned messages

• Transfer settings

• Radio settings

Settings permissions may include Read or Write access.

• Read: View configuration settings

• Write: Create or modify settings

Some platform capabilities fall outside the main categories.

Examples include:

• Managing spam acknowledgements

• Managing QA forms and evaluations

• Managing training content

• Viewing or exporting logging data

The Field Responder role allows responders to access incidents through shared links sent from dispatch.

These users can:

• View incident information

• Access shared media

• Respond through the first responder interface

Note:
Users with the Field Responder permission will not have access to the full dispatch interface.

Administrators can create roles tailored to their agency.

Examples include:

• Training Supervisor

• Advanced Call Taker

• RTCC Analyst

• QA Specialist

To create a role:

1. Navigate to Supervisor Settings

2. Select Roles & Permissions

3. Click Create Role

4. Enter a role name and description

5. Select the permissions to include

6. Save the role

Custom roles only apply to the specific dispatch center where they were created.

Roles are assigned through the Manage Users section.

When editing a user:

1. Select one or more roles

2. Save the user profile

Users can have multiple roles at the same time.

The system combines permissions from all assigned roles.

Example:

A user could be both:

• Calltaker

• Floor Lead

This would give them permissions from both roles.

Prepared previously used Agency Contacts as a separate concept from users.

Now, agency contacts are managed as standard user accounts.

Typically these users are assigned the Field Responder role.

This change simplifies user management and allows responders to be managed alongside all other users.

When configuring roles:

• Assign the least access needed for each role

• Create specialized roles for training, QA, or RTCC staff

• Review roles regularly to ensure permissions remain appropriate

• Avoid giving administrative permissions unless required

This helps maintain system security and operational clarity.

If you need help configuring roles or permissions, contact:

Support@prepared911.com