Skip to Content
ERPX Documentation — Your complete guide to the ERPX platform
ModulesUser ManagementSessions & Audit Trail

Sessions & Audit Trail

Use System Actions to manage active sessions and review recorded changes. These tools serve different purposes from Users → User Actions, which manages feature permissions.

Active Sessions

Go to: System Actions → Sessions

The Active Sessions screen lists sessions for your account. Review the device information, IP address, and activity details to recognize where you are signed in. The current device is identified in the list.

End Another Session

Find the session, click Terminate, and confirm. To close your other sessions together, click Terminate All Other Sessions and confirm Terminate All.

Terminating other sessions keeps your current device signed in. This screen manages your active sessions; it is not a history of every user’s login activity.

Audit Trail Report

Go to: System Actions → Audit Trail Report

The report shows recorded field-level changes across supported modules and tables. It helps answer who changed a record, when they changed it, and what the previous value was.

Generate a Report

  1. Set From and To for the date range.
  2. Narrow the report with Users, Modules, and Tables as needed.
  3. Click Generate Report.
  4. Review the results and move through the report pages if there are additional entries.

For a particular record, use the report’s record search where available, or open the record’s audit history when the application provides that action. A record-specific view focuses the report on that record.

Read the Results

ColumnWhat it shows
Date & TimeWhen the recorded change occurred
TableThe type of record affected
RecordThe affected record
Field ChangedThe field that was changed
Old ValueThe recorded value before the change
New ValueThe recorded value after the change
DescriptionA readable description of the change
Changed ByThe user responsible, or System for a system-recorded change

Sensitive fields such as passwords are shown as SENSITIVE instead of exposing their values. A masked value is not evidence that the underlying value was empty.

The report describes changes recorded by ERPX. It should not be treated as a complete record of every action or every time someone viewed a screen.

Troubleshooting

SituationWhat to check
No audit entries appearCheck the date range and selected user, module, table, or record filters, then generate the report again
A password value is unavailableSensitive values are intentionally masked
A session no longer appearsIt may have expired or been terminated; Active Sessions shows current sessions
A feature permission needs changingUse User Capabilities or User Actions, rather than the audit report