Audit Logs

Audit Logs provide a read-only history of important actions performed in the portal. Use them to answer questions such as who changed a record, when the change happened, which resource was affected, and whether the action succeeded.

When to use Audit Logs

Use Audit Logs when you need to:

• investigate a change;
• confirm who performed an action;
• review recent portal activity;
• support an internal audit or operational review.

Understand the Audit Logs screen

Each row represents one recorded action. The table includes:

Column	What it tells you
Time	When the action was recorded. Use this when matching the event to an incident or support request.
User Name	The portal user who performed the action.
Entity	The entity or customer context in which the action occurred.
Action	The type of operation, such as creating, updating, or deleting a record.
Resource	The type of configuration or record that was affected.
Status	SUCCESS means the action completed; FAILURE means it did not complete successfully.
Summary	A short description of the event.
Actions	Opens the detailed values captured for the event.

Find and inspect an action

1. Open Administration.
2. Select Audit Logs.
3. Use search and filters to narrow the list. Start with a user name, resource name, action, or status if you know it.
4. Check the Time, User Name, Action, Resource, and Status columns to confirm that you have the correct event.
5. Select the eye icon in Actions to view the previous and updated values.

The values panel displays structured data captured before and after the action. Unchanged or unavailable information may be empty. Technical field names can differ from the labels shown elsewhere in the portal.

Investigate a reported change

When reviewing a log entry, check:

1. Ask for the approximate time, affected record, and user who noticed the issue.
2. Search for the resource or user and check events around that time.
3. Confirm whether the event status is SUCCESS or FAILURE.
4. Open the values and compare the previous value with the updated value.
5. Record the event time and summary when escalating the issue to support.

Note

Audit Logs are evidence of portal activity, not an undo feature. To reverse a valid change, open the affected configuration page and make a new authorised change. If you are unsure, contact an administrator before editing production configuration.

If an expected event is missing

• Select Refresh to load recent activity.
• Clear or broaden the current search and filters.
• Confirm that you are working in the correct entity context.
• Remember that your role may restrict which audit records you can see.
• If an action failed before it reached the portal, there may be no completed change to display.