Knowledge Base

Every person in NoldusViso has an individual account with exactly one role. Roles define what a user is allowed to do — record, annotate, configure, manage users, and so on. This role-based model keeps access controlled and predictable across the platform.

• Each user has a unique account and exactly one role
• Roles determine capabilities, not visibility — see Departments and Groups for how visibility and ownership are scoped

This page applies to every user: understanding your role tells you exactly what you can and cannot do in NoldusViso.

Important note: Assigning roles is the organization's Administrator's responsibility, and directly affects security and privacy. Role assignment should be reviewed deliberately, not delegated casually.

Prerequisites

• NoldusViso must already be installed and configured by a Technician (Level 0).
• At least one Administrator (Level 1) account must exist before other user roles can be created.

User roles

NoldusViso defines five user roles, each with a distinct scope of action. Role names shown in the UI can be renamed (RBAC), these are the defaults.

Level 0 — Technician (system level)

• Can access the system via CLI and UI
• Can import recording media or portable bundles through technical/CLI workflows
• Can install, set up, configure, and maintain the system
• Can register devices
• Can perform license management
• Has access to advanced technical and system configuration functions
• Can create Administrator accounts
• Can rename RBAC role names in the UI
• Has full responsibility for system and data backups, including configuration, execution, monitoring, and auditability
• Can create and export audit reports

Level 1 — Administrator (organization level, UI only)

• Can manage system-wide settings
• Can manage all user accounts and access rights
• Can create, manage, and change user roles (Researcher/Trainer, Student/Trainee, Guest) and assign them to departments
• Can create and manage departments
• Can create and manage department-bound user groups
• Can perform license management
• Can register devices
• Can discover scenarios throughout the organization and configure scenarios in their own department
• Can add, edit, and save subjects, tasks, and events in same-department scenarios
• Can schedule, start, stop, save, and review any session
• Can define retention policies
• Can delete any sessions or files
• Can soft delete and hard delete users at Level 2, 3, and 4, while keeping ownership of sessions and files in mind
• Can transfer ownership of sessions and files

Level 2 — Researcher / Trainer (operational level)

• Can configure scenarios and select devices
• Can import recording media or portable bundles into the library
• Can add, edit, and save subjects, tasks, and events to own scenarios, or use ones already defined
• Can schedule, start, stop and save recordings of their own sessions and review them
• Can share sessions with Admins, Researchers/Trainers, Students/Trainees, and Guests
• Can define retention policies for own sessions only
• Can delete own sessions and files
• As the creator of a session, is its owner and can annotate, share, edit, and delete it

Level 3 — Student / Trainee (project level)

• Can discover scenarios in their current department, but cannot create or edit them
• Can join sessions shared with them
• Can watch as Viewer, read annotations as Reviewer, or add annotations as Annotator, according to the invite or link level
• Cannot start or stop recordings solely because a session was shared with them

Level 4 — Guest (session level)

• Can access the system via invite links
• Can view sessions that were explicitly shared or opened through an active link
• Sees annotations only with Reviewer or Annotator access; Viewer access is video-only
• Cannot create, edit, or configure anything

From scenario to session

Users with the right to do so follow this order of work:

1. Create a scenario — add everything needed to record and annotate: resources (audio, video, screen capture), subjects, tasks, and events.
2. Save the scenario — for later reuse, or to use it right away.
3. Open a saved scenario — edit and save it again if changes are needed.
4. Open the session and start recording — a Session is the collaboration context; starting Recording is a separate action inside it.
5. Annotate the session — score the observed behavior per subject, and add tasks, events, and notes to the timeline. This can be done live, while recording, or afterwards in replay.

Session ownership

A Session Owner must be a Researcher/Trainer or Administrator with access in the Session's department. Ownership grants Session control, including sharing, closing, and editing the active Session's coding scheme. It does not override department boundaries or silently grant the same changes to the reusable Scenario. Administrators also have the selected organization-wide live-Session operations; invite levels never appoint an Owner.

Links

• Departments and Groups
• System requirements
• Installation
• Getting started