Page body
What this page shows
Change Notifications is the main audit list for recorded backoffice and system changes.
Each row is one immutable audit event stored in the change-audit log.
When to use it
- find who changed a configuration or entity
- narrow the audit trail by change type, actor, or entity
- inspect the detail page for the full before/after payload of one change
- investigate support questions around recent administrator actions
How to read it
The grid is sorted by change timestamp descending. Each row summarizes:
- change id
- change type
- target entity type and id
- who made the change
- when it was recorded
- source IP and backend-generated description
The page is optimized for narrowing the audit trail first and opening the detail page second.
Filters that change the result
- start date
- end date
- change type
- changed by
- entity
- rows per page
Changing any filter resets the FE table page to 0. Changing rows per page also resets the table back to the first page.
Known caveats
- The page itself does not currently wire the export callback into the filter component, so visible
Export CSV/Export PDFbuttons are not mounted even though the backend export route exists. Reset FilterssetsStart Dateto seven days ago andEnd Dateto today. That differs from the initial route state, where both date filters start unset.- The FE dropdown and color map can lag behind the backend enum list. New backend change types may still appear with default styling.
Entityis a fuzzy search over bothentityTypeandentityId, not a strict single-column filter.Changed bysearches by name and also by numericchangedByIdwhen the search text parses as an integer.- Row click and the
View Detailsicon both open the same detail route.
Verification status
- status:
verified_backend - FE route, filters, table, and detail handoff are mapped
gs-admin-backendowns list reads, audit writes, export, and immutable storage semantics- no explicit
nx-workspacedependency is required for the current list surface