How audit evidence is filtered
The rules that decide which evidence a viewer sees in VoraAudit: organization, selected site, licensed products at the site, and the access of the viewer.
Everything visible in VoraAudit passes through the same filter chain before it renders. Understanding that chain explains both what appears at /audit and, just as importantly, why a record you know exists may not be on screen for a particular viewer.
The filter chain
- Organization: evidence never crosses companies; a viewer only ever sees records belonging to their own organization.
- Selected site: VoraAudit reads the site chosen in the VoraCore context in the topbar; records created at another site do not appear until you switch to it.
- Site entitlement: VoraAudit itself requires a VoraSuite package or the VoraAudit upgrade for the site; without it the evidence surfaces do not load.
- Licensed products: evidence sources only appear for products licensed at the site; a site without VoraTool shows no tooling, maintenance or spares evidence.
- Viewer access: within the licensed scope, records follow the access of the signed-in viewer, so two users at the same site can see different evidence.
Access follows the site, not the person
There is no per-user VoraAudit role. If the site entitlement includes VoraAudit, every user with access to the site can open it and sees the evidence their own product access allows. This is why VoraAudit does not appear in the per-user access modal alongside the product access levels.
Why a record may not appear
Work through the chain in order. Check that you are on the site where the record was created. Check that the product owning the record is licensed at that site. Check that the viewer holds access to that product area. In the Audit Reporter, also check the subject and time period filters; an event outside the selected period is filtered out, not missing.
No fake evidence, ever
VoraAudit renders only real records. It never pads a surface with dummy rows, sample data or invented counts, and an empty area states plainly that no evidence is recorded. If a source cannot be loaded, the home page lists it as a read issue instead of silently hiding it, so an auditor-facing view is never quietly incomplete.
Still stuck? Get support or contact the team. Support replies personally, typically within one business day.