Users & Roles
As an administrator, you manage the users in your organization. StoryVault uses a four-tier role system supplemented by additional capabilities.
Role Overview
Section titled “Role Overview”StoryVault has four roles that build on each other. Each higher role includes the permissions of the roles below it.
| Role | Description | Typical Use |
|---|---|---|
| Participant | View sessions explicitly assigned to them | External consultants, guests, observers |
| User | Create own sessions and projects, upload files, use search | Staff in day-to-day work |
| Manager | Start Meeting Bot, manage projects and sessions, create LMS courses | Team leads, QM officers |
| Admin | Full organization management: users, groups, invitations, costs, settings | IT administrators, management |
Capabilities
Section titled “Capabilities”In addition to roles, you can activate individual capabilities per person. These are independent of the role and allow finer-grained control.
| Capability | Description | Requirement |
|---|---|---|
| Learner | Work through courses, complete quizzes, track progress | None — available for all roles |
| Trainer | Create courses, edit lessons, configure quiz questions | At least “Manager” role |
Creating a User
Section titled “Creating a User”-
Open user management
Sidebar → Admin → Users.
-
Click “Create User”
Enter name, email address, and password (or have a password auto-generated).
-
Select a role
Choose the appropriate role: Participant, User, Manager, or Admin.
-
Set capabilities
Enable “Learner” and/or “Trainer” as needed.
-
Set project access
Determine which projects the user may see. Admins automatically have access to all projects.
-
Save
The user can log in immediately.
Editing a User
Section titled “Editing a User”Click on a name in the user list to open the profile. Here you can:
- Change the role — for example promote from User to Manager
- Adjust capabilities — enable/disable Learner or Trainer
- Change project access — assign new projects or remove existing ones
- Deactivate the account — the user can no longer log in, but their data is retained
Project Access and Visibility
Section titled “Project Access and Visibility”Visibility of content depends on role and project membership:
- Admin — sees all projects and sessions in the organization
- Manager / User / Participant — sees only projects they’re assigned to and their own sessions
In practice: if the disability support and senior care teams use separate projects, a user from the disability support team cannot see senior care content — unless they’re assigned to both projects.
Further Reading
Section titled “Further Reading”This page corresponds to the onboarding video “Module 7, Lesson 7.1 — Creating Users and Assigning Roles”.