Study Audit Trial Navigation

To access the Study Audit Trail, navigate to the study and click Settings Study Audit (as below).

All study data changes performed by either a user or by the system is documented in the Study Audit Trail.

Each entry includes the following information:

  1. Date: the date and time when the change was requested
  2. Action: the type of change that was performed
  3. Requester: who triggered the action (user via UI or via API, or the system) - see details below
  4. Rationale for change
  5. Old and New Values (To access, expand a row by clicking on it.)

To Export Study Audit Trail for offline review in .csv format, click Download as CSV. (The downloaded file will include all existing study audit entries. You can filter entries to be downloaded by time period.)

To navigate to the Study Audit Entry page, click the squared arrow icon at the end of each row (as seen below).

In addition to the fields listed above, the Study 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 Study Audit Trial:

Requester displayed in Study Audit Meaning
User name (or user email) Action performed by a user from the company in MyRBQM where the study is
System Action performed automatically by the system (e.g., ticket creation)
Company (via API) Action performed via the Integration API
User Name (blocked) or (deleted) Action performed by a user who is currently blocked or deleted
internal user ID, if available (user not found) User not found in the MyRBQM user database
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us