Plugin Events
Plugin events are what people did once they were inside: queries run, cameras viewed, alerts handled, subjects opened, reports generated, module views visited.
Each is an audit record, so this view is the audit trail queried across everybody.
Querying by action
Every action carries a type with a human label — View Camera, Query, Alert - Acknowledge, Module View Opened. Filtering by type is how you ask "who did this?" rather than "what did they do?"
The Audit Catalog lists every type with the exact text it records, which is what makes precise searching possible. Consult it before searching rather than guessing at wording.
Searching descriptions
Descriptions follow fixed forms, so they can be searched for a pattern:
| Looking for | Search on |
|---|---|
| Camera viewing | CAMERA ' |
| One camera | CAMERA 'North Entrance' |
| Alerts ignored | ALERT IGNORED |
| Periods of muting | ALERTS MUTED |
| Data leaving via export | QUERY EXPORT |
| Face searches | SEARCHED FOR FACE |
Adoption
Aggregating Module View Opened by module tells you which parts of eConnect are actually used.
That is a genuinely useful management figure: it shows whether training landed, whether a licensed module is earning its cost, and where to concentrate effort. Navigation is audited precisely so this question is answerable.
This action is recorded in the audit trail.
Duration, not just access
Some actions record how long something was engaged with, not merely that it was opened:
This action is recorded in the audit trail.
Aggregating that answers "how much footage review is actually happening?", which is a different and usually more interesting question than how often cameras were opened.
Data leaving the system
Exports are audited, so QUERY EXPORT finds what has left eConnect as files, when and by whom. That
is often the first thing asked after a data-protection query, and it is answerable here in seconds.
This action is recorded in the audit trail.
Use it proportionately
This view makes it easy to watch colleagues in detail. Access should be narrow, and the purpose should be a real one — a security question, an access review, a support investigation.
Querying it is itself audited, which is as it should be.
Audit record
What eConnect writes to the audit trail for the actions on this page.
MODULE VIEW OPENED '{title}'
CAMERA '{camera name}' REVIEWED FOR {elapsed}
QUERY EXPORT '{name}' FROM {start date} to {end date}