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.
Top-level areas
Section titled “Top-level areas”On the left is a dark side panel, the rail: it switches between work areas. An area is not shown at all if you do not have a single applicable permission. The rail can be collapsed to icons with “Collapse sidebar”; on a phone it opens from the burger button.
| 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 | all your work in one place | you have at least one task source |
| Admin | access, users, modules, settings, audit, inspection | you have at least one admin permission |
Profile is not a work area but your personal settings: it opens from the user menu (your avatar and name on the right of the top bar), and on a phone from the rail’s footer.
Inside a study, section navigation appears on the left in three layers: Work (Overview, Subjects, Queries and your role’s queue — SDV, Medical Review, Coding or Signatures), Control & closeout (Monitoring, Audit trail, Locks, Exports) and Setup (Design, Sites, Team, Randomization, module reference lists). An item is shown to those whose work it is: items you do not have rights to simply are not shown. Event delivery and outgoing mail live in Admin → Settings, the “System” section.
What the section shows depends on the study’s phase. While the study is a Draft, it is being built: the rail shows only Overview and the Setup items. In a launched study Work and Control & closeout come first, and Setup collapses into a single item with tabs.
Breadcrumbs: “where am I”
Section titled “Breadcrumbs: “where am I””The top bar carries 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:
In progress · 12/18 Pending · 7 Open · 3 Signed · 4/12 Not locked
Each badge is also a filter link: clicking the open-queries badge 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).
Action panel: “what can I do”
Section titled “Action panel: “what can I do””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.
Language, theme, and profile
Section titled “Language, theme, and profile”- Interface language. The ru/en switcher is in the user menu, the “Language” row (on a phone — in the rail’s footer). 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 in the user menu (“Light” / “Dark”) 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.