Summary
StockIQ keeps an audit trail of changes made in the web app: who made each change, when, and the old and new values. Admins review it at Admin > Audit Trail. The screen is a grid of changes with a detail pane, and requires the View Audit Trail permission. This is separate from Usage Log access.
What Gets Recorded
- Who made the change: every entry names the caller and its type: a user, Edison, an API token, or an integration. Changes Edison makes for a user are recorded as Edison. Names remain visible even after a token is revoked.
- Only completed changes: an entry is written after a change succeeds. Saving without changing anything writes no entry.
- Secrets stay hidden: passwords, token values and ERP connection passwords are masked. The entry still shows that the value changed.
- Filters: date range (the last 30 days by default), caller type, change type, record type, record id, item-site and hierarchy node. Up to 5,000 rows are returned.
- Detail pane: select an entry to see each Field with its Old Value and New Value.
- Empty values are shown three ways: "(not recorded)" means no value was captured, "(none)" means the field had no value, and "(blank)" means it held empty text.
How Long History Is Kept
Set the retention on Global Data Settings with "Max days of configuration change history to keep in the audit trail." The default is 1,095 days (3 years), and it can be set from 365 to 3,650 days. It is separate from Usage Log retention, so shortening one never shortens the other.
What Is Not Recorded
- Results StockIQ recalculates, such as forecasts and suggested orders.
- Data loaded from your ERP feed, which is tracked in the import history.
- Personal display preferences, such as saved views and layouts.
- Some bulk planning actions, such as forecast edits and orders placed through the order wizards.
Not Available Yet
- Reverting a change from the audit trail.
- Filtering on a hierarchy node together with its parents or children.