Roles & Permissions
crisisIQ uses role-based access control (RBAC) to determine what features and actions are available to you.User Roles
There are four main roles in crisisIQ:Participant
Join and complete training simulations
Content Creator
Build scenarios and training materials
Company Admin
Manage organization and users
System Admin
Full platform administration
Participant Role
Primary Function: Engage in training simulationsPermissions
- Can Do ✓
- Cannot Do ✗
- Join assigned group simulations
- Complete solo training exercises
- Make decisions during simulations
- Communicate with team members and AI Mentor
- View personal performance reports
- Download earned certificates
- Update own profile and settings
Typical Use Cases
- Employees: Undergoing crisis management training
- Team Members: Participating in group exercises
- Learners: Completing solo training modules
- Trainees: Building skills through practice scenarios
Participants must have verified email addresses to join most simulations.
Content Creator Role
Primary Function: Design training scenarios and contentPermissions
- Everything Participants Can Do, Plus
- Cannot Do ✗
- Create new scenarios
- Edit existing scenarios
- Build timeline events and sequences
- Upload and manage media resources
- Preview scenarios before publishing
- Duplicate and modify scenarios
- Access scenario analytics
Typical Use Cases
- Trainers: Developing custom training materials
- Subject Matter Experts: Creating realistic scenarios
- Instructional Designers: Building educational content
- Facilitators: Preparing simulation exercises
Scenario Builder Access
Content Creators have access to:- Scenario Wizard: Step-by-step scenario creation
- Timeline Builder: Visual event sequencing
- Decision Designer: Create decision points and options
- Media Library: Upload documents, images, videos
- Assessment Tools: Define scoring criteria
Creating Scenarios
Learn how to build scenarios
Company Admin Role
Primary Function: Manage organization and training programsPermissions
- Everything Creators Can Do, Plus
- Cannot Do ✗
- Manage all company users
- Send invitations and generate join codes
- Assign and revoke roles
- Create and assign simulations
- View all participant reports
- Access company-wide analytics
- Configure company settings
- Manage teams and groups
- Archive and delete scenarios
Typical Use Cases
- Training Managers: Overseeing organizational training
- HR Leaders: Managing employee development
- Department Heads: Coordinating team training
- Program Directors: Running comprehensive training programs
Admin Features
Company Admins can access:User Management
Invite, edit, deactivate users
Assignment Control
Assign simulations to individuals or teams
Company Reports
Organization-wide performance analytics
Settings
Configure company preferences
User Management Guide
Learn how to manage users
System Admin Role
Primary Function: Platform-wide administrationPermissions
- Full Access
- Responsibilities
- All Company Admin capabilities across all organizations
- Manage multiple companies
- Create new organizations
- Access system settings
- View platform audit logs
- Monitor system health
- Configure platform-wide defaults
- Access database and logs
System Features
System Admins have unique access to:- Company Management: Create, configure, archive organizations
- Global Settings: Platform-wide configuration
- Audit Logs: Security and activity monitoring
- User Support Tools: Impersonate users for troubleshooting (with proper authorization)
- System Health: Performance monitoring and alerts
Permission Matrix
Here’s a quick reference of what each role can do:| Feature | Participant | Content Creator | Company Admin | System Admin |
|---|---|---|---|---|
| Join simulations | ✓ | ✓ | ✓ | ✓ |
| Solo training | ✓ | ✓ | ✓ | ✓ |
| View own reports | ✓ | ✓ | ✓ | ✓ |
| Create scenarios | ✗ | ✓ | ✓ | ✓ |
| Edit scenarios | ✗ | ✓* | ✓ | ✓ |
| Assign simulations | ✗ | ✗ | ✓ | ✓ |
| Manage users | ✗ | ✗ | ✓ | ✓ |
| View all reports | ✗ | ✗ | ✓ | ✓ |
| Company settings | ✗ | ✗ | ✓ | ✓ |
| Manage companies | ✗ | ✗ | ✗ | ✓ |
| System settings | ✗ | ✗ | ✗ | ✓ |
Multiple Roles
Users can have different roles in different organizations:Example
You might be:- Company Admin in Organization A (your employer)
- Participant in Organization B (partner training)
- Content Creator in Organization C (freelance work)
Managing Multiple Roles
1
Use Company Switcher
Select the organization you want to work with
2
Role Updates Automatically
Your permissions change based on your role in that company
3
UI Adapts
Navigation menu shows features available to your current role
4
Context Maintained
Each organization maintains separate data and settings
Checking Your Role
To see your current role:-
Look at the Company Switcher dropdown
- Shows your role next to each organization name
-
Check your Profile page
- Lists all organizations and your role in each
-
Note the Navigation Menu
- Available features reflect your current role
Role Requests
If you need a different role:1
Contact Your Admin
Reach out to your organization’s Company Admin
2
Explain Your Need
Describe why you need the role (e.g., “I need to create scenarios for my team”)
3
Admin Updates Role
Admin can promote or change your role
4
Refresh Your Session
Log out and back in to see updated permissions
Only Company Admins (or System Admins) can grant or revoke roles. Role changes take effect immediately but may require a page refresh.
Role Best Practices
For Participants
Complete assigned simulations before deadlines
Review feedback and reports to improve
Verify your email for full access
Update your profile with accurate information
For Content Creators
Test scenarios before publishing
Use descriptive names and tags
Provide clear instructions in scenarios
Keep media files organized
For Company Admins
Grant minimum necessary permissions
Regularly review user access
Remove access for departed users promptly
Use groups/teams for easier management
For System Admins
Monitor platform security regularly
Document configuration changes
Maintain audit trails
Communicate platform updates to users
Security & Access Control
Role Security Features
Principle of Least Privilege
Users get only the permissions they need
Audit Logging
All role changes are logged
Session Management
Roles enforced in real-time
Company Isolation
Roles are scoped to organizations
What’s Protected
- Data Access: Users see only what their role permits
- API Endpoints: Backend enforces role-based access
- UI Elements: Features hidden if not permitted
- Audit Trail: Who did what, when, in which role
Troubleshooting Permissions
I can't see a feature I need
I can't see a feature I need
- Check your current role in the Company Switcher
- Verify you’re in the correct organization
- Contact your admin if you need elevated permissions
- Confirm your email is verified (required for some features)
My role changed unexpectedly
My role changed unexpectedly
- An admin may have updated your permissions
- Check with your organization administrator
- View audit logs if you’re an admin
Can't access after role update
Can't access after role update
- Log out and log back in
- Clear browser cache
- Verify the role change was saved (check with admin)
Need higher permissions temporarily
Need higher permissions temporarily
- Contact your admin to request temporary elevation
- Explain the specific task you need to complete
- Admin can grant and later revoke the role