Articles in this section

How to Verify Acting User Details in Bold BI Activity Logs (v15.3.8+)

Published:

Starting from Bold BI Server v15.3.8, Bold BI has included an improvement to record the acting user more accurately for add, update, and delete actions.
This article explains how administrators can verify this behavior by using the Audit Logs page in Bold BI on premise.

Step-by-Step Instructions

1. Confirm your Bold BI Server version is v15.3.8 or later. If you are on an earlier build, consider Upgrading Bold BI Server to v15.3.8+

image.png

2. Sign in to Bold BI Server as a System Administrator.

image.png

3. On the UMS page, click on the Settings (gear) icon.

image.png

4. From the Settings menu, select Audit Logs to open the audit log page (User Activity Logs).

image.png

5. Perform one add/update/delete action that should be audited.

Example actions you can test:

  • Add or delete a user.
  • Update dashboard permissions.
  • Delete a dashboard or data source.
6. Filter the logs to find your event.

In User Activity Logs, use filters such as:

  • Event Category (for example: User, Permissions, Settings)
  • Event Type (Added, Updated, Deleted)
  • Date/time range
    image.png

    image.png

    image.png
7. Open the log entry details for the event.

Click View (or the equivalent details option) for the relevant row.

image.png

image.png

8. Confirm the “User” field shows the acting user (the person who performed the action).

Expected result (v15.3.8+):

  • The User field reflects the actual actor, even if:
    • An administrator changes/deletes resources owned by another user
    • The action is triggered from embedded or API-based workflows (when a valid user context is used)

If you are using embedded or REST API workflows, ensure your implementation is passing valid user context for requests. Verify exact headers/claims/session behavior used by your embedding model
Reference:

Related official documentation

Was this article useful?
Like
Dislike
Help us improve this page
Please provide feedback or comments
EO
Written by Erick Oloo Awino
Updated:
Comments (0)
Access denied
Access denied