Skip to content

How RIQS is organised

In one sentence: RIQS is built in layers: a group can hold several organisations, an organisation holds one or more units, and every user works in at least one unit.

The building blocks

Group  (optional)
└── Organisation        e.g. "Medical Centre North Ltd."
    ├── Unit            e.g. "Practice Zurich"
    │   ├── Users
    │   └── Unit data   (documents, shift plans, tasks, equipment, reports …)
    └── Unit            e.g. "Practice Basel"
        └── …
Level What it is Example
Group Several organisations that are managed together A chain that owns several companies
Organisation The customer company. It holds the subscription, billing and organisation-wide settings "Medical Centre North Ltd."
Unit One team, site or practice inside the organisation. Almost all daily work happens at unit level "Practice Zurich"
User A person who logs in. Each user has one primary unit and may also have access to other units A nurse working in Zurich who sometimes helps in Basel

In some screens of the app, a unit is called a Client. They mean the same thing.

Organisation level vs unit level

Most things in RIQS live inside one unit, for example a shift plan, a task list, a device or an incident report. Only the people of that unit (and admins above them) see it.

Some things can be set up at organisation level so that they apply to all units:

  • documents and folders in RiQS-Pedia that the whole organisation shares
  • officers who act for the whole organisation (for example a CIRS Officer for the organisation)
  • subscription, licences, AI tokens and storage, which the organisation can share out to units

Each module page explains which of its items can live at organisation level.

Primary unit and switching units

  • When you log in, RIQS opens your primary unit.
  • Administrators (RiQS Administrator, Group Administrator, Administrator) can use the unit switcher at the top of the screen to change to another unit at any time. They don't need to log in again.
  • Other users who belong to more than one unit choose the unit when they log in.
  • What you see (menu, data, buttons) always belongs to the unit you are currently in.

Audit-safe mode

Some customers must keep a full, unchangeable record for audits. For them, RIQS can run in audit-safe mode:

  • In the regular version, authorised users can delete records.
  • In audit-safe mode, deleting is blocked for client users. Normally only the RiQS Administrator can delete. Users deactivate items instead, so the history is kept.

The permission tables on every module page show both cases where they differ.

What decides what a user can see?

Three things together:

  1. Subscription. Is the module part of the organisation's package? If not, the menu entry is hidden for everyone.
  2. Role. What is the user allowed to do? See Roles & permissions.
  3. Assignment. Some items are only for specific people, for example a restricted document, an assigned task or a training someone was invited to.

Last reviewed: 2026-10-26