Account Activity and the Security log

Checked against the product’s code on 7 November 2026.

Open Activity in your Praxis account. The Security log describes recorded account actions in plain words. It is separate from the site’s copilot Activity. Only account owners and Admins can read the Security log, with or without network addresses.

If the page could not read the Security log, reload it as the message asks. A failed read does not mean there are no events. The no-events message is reserved for a log that was read and is empty.

Read the entries

1. Read the action.
2. Read its time.
3. Read the person or service recorded beside it.

The account labels our staff’s actions Praxis staff, or Praxis staff, with the copilot when they used the staff copilot. Your own team’s actions can show a name or email; your copilot reads Your copilot. Platform work reads Praxis. Download CSV includes the same readable actor labels.

When our staff save a new internal note, the Security log records the activity’s reference without the note’s words. The note stays in staff tools.

Each support entry reads as a plain sentence, such as Issued a read only support entry link for the account. Reasons given for a grant, emergency access or an Admin override are stored with those records and appear in Download CSV, a spreadsheet file, within the same site scope as the log. The log records when support was given access, when that access was revoked and when an entry link was issued. The service also tries to record when a staff visit ends, including sign out. A failed end record is logged on the server and does not keep the visit open. The platform’s regular run can record a missing end after an eligible grant expires. That entry says it was recorded later and that use of the entry link after the last recorded action is not known.

The address shown with an entry follows the logging mode of the site it belongs to. A network only record does not contain the same detail as a full address record. Changing that mode applies to later entries.

Keep a copy

Account owners and Admins can read and export the Security log. The menu beside the log can copy or download the 25 rows on the page you are reading. Download CSV saves the newest 10,000 entries. Downloading it is itself recorded.

1. Open Activity.
2. Use Prev or Next to reach the page you want to inspect.
3. Read the site scope described below before exporting.
4. Open the menu beside the log.
5. Choose the copy or download action for those 25 rows, or Download CSV for the bounded export.
6. Keep the file’s scope and capture-time lines with it.

The CSV starts with lines that state its scope and when it was captured; keep them with the file. It includes records for the site your account was opened with and the permitted creation, readiness and support access records from the account’s other sites. It follows the same site scope as the log.

Support entries into any site in the account appear in your Security log and its CSV export. Reading across sites requires an active owner or Admin membership on an active or suspended site in that account.

Entries for a fully erased site no longer appear. Without that active membership, the log and export show only the site your account was opened with. That limit applies throughout the account’s closing period when all its sites are being closed or have closed. Changes made inside a site are recorded in that site’s copilot Activity.

Understand verification

Log entries use SHA-256 checksums, digital fingerprints that link each entry to the previous entry in the platform’s audit log. Editing or deleting an earlier entry breaks the chain. The platform checks the whole chain every night with tamper-evident checks of the recorded entries and their links. The check identifies four recorded gaps from 19 August 2026. This account screen does not display a completed chain verification result.

Amadalis staff run the check across the platform’s log. Your CSV contains only its permitted account and site rows. Ask support for the current result and its scope.

Account erasure is designed to remove personal details without breaking the check. These checks do not protect against someone who controls the database.

For session rules and support grants, use Account Security. For visitor records and erasure, use Visitor Data.