Audit Trial Navigation
The MyRBQM® Portal records all actions performed by a user or system during the study in the form of an audit trail. The audit trail is presented at two levels: Company and Study. Portal administrators can access both levels via the Audit Manager.
To access the Company Audit Trail, click Settings → Company Audit in the header menu. To access the Study Audit Trail, navigate to the relevant study and select Settings → Study Audit (as shown below).
NOTE: The Study Audit can only be accessed from the Settings dropdown menu after a study has been opened.
Each entry includes the following information:
- Date: the date and time when the change was requested
- Action: the type of change that was performed
- Context: a link to the item the change was performed with
- Requester: who triggered the action (user via UI or via API, or the system) - see details below
- Rationale for change
- Old and New Values (To access, expand a row by clicking on it)
To export the Audit Trail for offline review in .csv format, click Download as CSV. The downloaded file includes all existing audit entries. You can filter the entries by time period before downloading.
To navigate to the Audit Entry page, click the square arrow icon at the end of each row (as shown below).
In addition to the fields listed above, the Audit Entry page includes a Request and Response Details section, where you can find:
- Request Details: Information about the specific action and its parameters that was requested by a user or in some other way (API Request)
- System Response Details: The system’s reply to the request, including any returned data or error messages (API Response)
Each audit entry page has its own unique ID and can be shared with other users by sharing the page link.
Types of Requesters displayed in the Audit Trial:
Each audit entry in the Company and Study Audit Trails has a requester — a person or a system that triggered the action:
Below are the definitions of each requester type.
| Requester displayed in Audit | Meaning | Level of Audit |
|---|---|---|
| User name (Global Administrator) | Action performed by a Cyntegrity employee: initial company setup or editing of company configuration | Company and Study |
| User name | Action performed by a user from the company in MyRBQM where the study is | Company and Study |
| System | Action performed automatically by the system (e.g., ticket creation) | Study |
| Company (via API) | Action performed via the Integration API | Company and Study |
| User Name (blocked) or (deleted) | Action performed by a user who is currently blocked or deleted | Company and Study |
| internal user ID, if available (user not found) | User not found in the MyRBQM user database | Company and Study |
The user name is displayed according to the following priority:
- If the user’s name is defined in the portal, it is displayed.
- If the user’s name is not available, the email address is displayed (if available).
- If neither the user’s name nor email address is available, the GUID (user’s internal ID) is displayed, followed by “(user not found)”.
- If none of the above information is available, “User not found” is displayed.