Create, update, delete
The three that matter, each filterable.
Operations · Audits
Who changed it,
and when.
The question nobody asks until they have to. A rate board goes out wrong, a notice disappears, a price is not what was signed off — and the only useful answer is a name and a timestamp.
Plans, prices and trials are set by your ScreenQube partner.
Where it ends up
You work in a browser.
They see the wall.
The screen above is what you publish. This is where it ends up.
How it is made
What is actually behind it.
Named against the product's own modules rather than invented for a marketing page.
-
Every action, typed
Created, updated, deleted — filterable by which.
-
An actor against each
The person, not just the account.
-
A time against each
Performed On, so a sequence can be reconstructed.
-
Filtered by resource
Facilities, users, compositions, media and the media repository.
What you get
Six things it does today.
An actor column
Who did it.
A performed-on time
When.
Filters by resource
Six resource types, so the log is searchable rather than endless.
An Audit Report
The log as a report you can keep.
For the review you did not plan for
Compliance, incident, or an argument with a supplier.
Who runs this
The industries that ask for it.
Nearby
Solutions that go with it.
Questions
The things people actually ask.
How long is history kept?
Not something we can state from outside the product. If a retention period matters to your compliance team, ask before you evaluate further.
Can we export it?
There is an Audit Report alongside the log.
Does it log playback as well?
No, and the distinction matters: Audits records what people changed. The Media Report covers what screens played. They are two different reports.
Can we restrict who sees it?
Users belong to groups, and groups decide what a person can reach.