Guide · Administration

Settings, visit recording and the audit log

For administrators: the organisation's name and logo, how visits are recorded and kept, and the audit log.

Updated 31 October 2026

Settings

Settings shows the Organisation name, which appears on the pages people see when a code is paused, archived or not yet live. Where Core home keeps the organisation's details, change the name there.

Public address of codes is the address every dynamic code holds. It is set when the service is deployed and never changes.

Under Logo for codes, choose a PNG or JPEG of up to 2 MB and Upload it. Editors can then put it in the middle of a code. Remove the logo takes it away.

Visit recording

Visit recording is linked from Settings. Every request to a code's address is recorded, without its IP address.

  • Is it working? and Recording gaps: times the service could not record requests. People were still sent on; the lost requests are listed, never estimated.
  • Scanner repeats: the window, from 0 to 60 seconds, in which repeats by the same estimated visitor count as one eligible visit.
  • How long figures are kept: months of detailed records, hourly figures and daily figures. Details are summarised before they are removed, so totals are never lost. These are product defaults, not your organisation's retention policy: confirm them with whoever owns that.
  • Automated visitors: text in a browser's user agent that marks its requests as monitoring, link previews or crawlers rather than visits.

Audit log

Audit log shows the latest 200 changes: when, who, the action, what it was about and the result. Entries cannot be edited or removed.

Was this helpful?