Roles in the System and User Access

You will learn about different user types on the platform, their permissions, and access methods. This knowledge will aid in assigning roles within your team, understanding integration options with other systems, and considering key limitations.

User Categories   

The platform divides users into two key categories: content creators (“Authors” and “Administrators”) and participants. Each role has a different level of access.

"Author" and "Administrator" access is set up manually by our team.

Roles for Content Management: “Authors” and “Administrators”  

The Author and Administrator roles are intended for employees responsible for creating and editing scenarios, as well as analyzing results.

The key difference between these roles lies in the scope of information visibility:

  • An “Author” works only within their own materials.

  • An “Administrator” can access content across the entire organization.

Let’s take a closer look at what each role can do:

PermissionAuthorAdministrator

Creating scenarios

Yes

Yes

Editing scenarios

Only their own

All scenarios in the system

Previewing scenarios

Only their own 

All scenarios in the system

Exporting SCORM packages

Only their own

All scenarios in the system

Inviting participants to play a scenario (sharing links)

Own scenarios only

All scenarios in the system

Deleting scenarios

Only their own

All scenarios in the system

Access to analytics (roleplay completion reports)

Only their own 

All scenarios in the system

Access to system settings (subscription information)

No

Yes

💡 If your team of "Authors" needs to collaborate on editing scenarios or reviewing colleagues’ analytics, consider assigning the Administrator role to several responsible team members.

⚠️ If your organization has multiple authors and administrators, note that any of them can edit a scenario's text. Changes are saved immediately, and previous versions cannot be restored.

Trainee access (participants / learners)    

Training participants use guest access. They don’t need an account, login, or password —just open the scenario link and enter their name before starting.

Advantages:

  • Extremely simple onboarding for users.

  • Minimal data collection — the system only stores the participant’s name.

⚠️ Important drawback: No unique identification. The system does not create a permanent profile for a participant. Therefore, if one person logs in from a work computer and a phone, they will appear in the analytics as two different participants. The same will happen if they enter their name differently each time.

Nex Steps

Set up the appropriate role and start working with the platform:

Need Help 

Write to us in the chat — we're always happy to help 💬

👆 You’re all caught up