Access log
Every request, decision, sign-in and download of your gated trust center documents, and who changed what is on offer.
What it is
The access log is the record of everything that happened around your gated trust center documents: who asked for access, who confirmed their email and accepted the NDA, what your team decided, who signed in, what they downloaded, which downloads were refused, and which settings, NDA versions and documents a member changed. It is written as things happen and cannot be edited.
Where to find it
Trust CenterAccess logThe view appears once access requests are available to your organization. The newest event is at the top.
Key actions
Read one kind of event
The tabs narrow the log: Downloads, Decisions, Requests, Sign-ins and Changes. All shows everything.
Follow one viewer
Click a person's name in the log, or Log on their row under Viewers, to see only their events: when they were approved, each sign-in and every document they downloaded. The Viewer token next to the tabs shows whose log you are reading; its × goes back to everyone. The tabs keep working inside one viewer's log.
Read further back
The page shows the latest 100 events. Show older entries at the bottom adds the next 100.
Statuses and fields
Each row says what happened, a second line with the detail (the document, the duration of an approval, why a download was refused), the person it concerns, who did it, the IP address and the time.
| Status | Meaning | Set by |
|---|---|---|
Access requested, Email confirmed, NDA acceptedrequests | A visitor sent the form, proved their address, and accepted the agreement. | The visitor |
Access approved, Request denied, Access revoked, Access extended, Access expireddecisions | A decision about someone's access. Expiry is recorded by the daily job. | A member, an API key, or Noru |
Signed in, Signed outsign_ins | A viewer opened or closed a session on your trust domain. | The viewer |
Downloaded, Download refused, Sent without a watermarkdownloads | A file left, a gated file was asked for without access, or a file could not be stamped. | The viewer or a visitor |
Access settings changed, NDA changed, Document added, changed or removedchanges | What is on offer, or the rules for it, changed. | A member |
The By column reads Viewer for a signed-in viewer, Visitor for someone on the public page who is not signed in, a member's name for your team, API key for a decision made through the API, and Noru for the daily expiry job.
Tips and gotchas
Download refused rows are the ones to look at after sharing a link widely: they show a gated document being asked for by someone without access. The visitor only ever sees "not found".
A public download is logged without a person: nobody is signed in, so there is only the document, the IP address and the time.
What Noru does not do
Noru does not export the log to CSV yet, does not alert on unusual download patterns, and does not delete log entries on a schedule. Hovering an IP address shows the browser's user agent; Noru does not resolve addresses to a location or a company.
Related
Last updated on