Skip to content

How the interface works

All of X7 Insight is a single shell with one screen frame. Once you have mastered one level of the hierarchy, you can find your way around any of them: the header, breadcrumbs, action panel, and right-hand panel all work the same way everywhere.

0:000:00
A tour of the workspace: from the study list into a study's sections.

The top bar switches between work areas. An area is not shown at all if you do not have a single applicable permission.

Area What it is for When it is visible
Studies list of studies and entry into the data hierarchy you have access to at least one study
Tasks “My queue” — all your work in one place you have at least one task source
Administration access, users, modules, settings, audit, inspection you have at least one admin permission
Profile language, time zone, current principal always

Inside a study, section navigation appears on the left. At the top is Overview (the study summary); below it the sections are grouped by work phase: Setup (Design, Sites), Data (Subjects, Queries), Monitoring (SDV, Medical Review, Signatures), Closeout (Amendments, Locks, Exports), Reporting (Reports, Audit). Items you do not have rights to simply are not shown.

Below the top bar runs a chain of breadcrumbs — a visualization of your current position in the data hierarchy (scope):

Each breadcrumb is clickable and leads to the screen for its level. This same hierarchy — study → site → subject → visit → form — also determines the page URL and which permissions are checked. One structure for navigation, addressing, and access.

Header and status badges: “what’s next”

Section titled “Header and status badges: “what’s next””

Below the breadcrumbs is the header of the current entity and a set of status badges along independent axes. For a subject, for example:

Entry 12/18 SDV 7 pending 3 open queries Signed 4/12 Not locked

Each badge is also a filter link: clicking “3 open queries” opens the slice of that subject’s queries. A badge is not shown if the corresponding axis is not visible to you (for example, the SDV badge requires the permission to see verification statuses).

To the right of the header is the action panel. Its contents are computed on the server: the system takes the list of possible actions and keeps only those allowed to you in the current scope.

  • An unavailable action is not rendered — not a “grayed-out button,” but absent entirely.
  • The exception is an action that is impossible due to state (a lock, a status): such a button is visible but inactive, with an explanation of the reason (“Form is locked”), because that is part of the “what’s next” answer, not a secret.
  • Interface language. The ru/en switcher in the top bar (labeled “Interface language”). The locale changes only the labels — URLs and data do not change, and the audit trail is not affected. You can set the default language in the Profile section.
  • Light / dark theme. The theme switcher (“Dark theme” / “Light theme”) changes the appearance without affecting content.
  • Profile. Also here: the display time zone (timestamps are stored in UTC and shown in the selected time zone) and the current principal.

Permission-gated UI: you only see what you are allowed to

Section titled “Permission-gated UI: you only see what you are allowed to”

The main rule of the interface: an action or section is displayed only when you have permission for it in the current scope. This is a navigation convenience, not a security measure in itself — the server rechecks every action anyway and responds with a denial if the permission is missing.

That is why two people on the very same screen can see different things: the coordinator can enter data, the monitor can mark SDV, the data manager can apply locks. If you cannot find an expected button or section:

  • most likely, you do not have the corresponding permission in this scope;
  • sometimes the system tells you directly whose workspace it is (for example, “The SDV workbench is unavailable to you: source data verification is the monitor’s workspace”);
  • you can request the missing access from your administrator — see Managing access.