Activity and the audit trail
Every change made to your network, in plain words: what changed, when, and who made it. Save it for a spreadsheet or for your own monitoring.
See what changed
Activity is part of the Organisation plan. Every change to your network is an entry in its signed log: who was approved, added, removed or renamed, every rule, every setting, every licence and update decision. Activity shows that log in plain words, so you can answer "who did what, and when?".
- Open the network, then Administer, then Activity.
- Read down the list, newest first. Each row is one change: what it did, when, and who made it.
- For more, choose Show earlier changes at the bottom: the list shows 100 at a time.
Command line
On Windows, in Terminal (Admin), once you have set $mt and $st. On Linux, in a terminal. Before you start
The whole history, oldest first:
& $mt audit $st northwindsudo multitunnel audit /var/lib/multitunnel northwindOnly changes since a date (UTC), or since a time such as 2026-11-01T09:00:00Z:
& $mt audit $st northwind -since 2026-11-01sudo multitunnel audit /var/lib/multitunnel northwind -since 2026-11-01-since leaves out entries with no time, which only very old logs have.
Who can see it
The network's administrators
On a computer that holds one of the network's current admin keys. A removed administrator's computer shows nothing. Several administrators
Not members
People in the network don't see it, and neither does a device you've let approve devices for a day: a delegation adds devices, it isn't an administrator's view.
Not a secret, though
Every device holds the network's log, because it needs it to check who belongs. Activity is about what MultiTunnel shows, not about hiding the log.
What it shows, and what it never shows
- What changed
- In plain words, such as "Approved dana-laptop for Dana Shah". A change made by a newer MultiTunnel than the one showing it says so, with its signer, number and hash as usual.
- Who made it
- By name, which is only a label, and by what identifies it for certain: an admin key's code, or a device's ID. Most changes are made by an administrator. A device makes its own leaving, its person's own name changes, and its right to add one more device for its person; the device it then adds is credited to it. The recovery key makes a recovery.
- The entry's number and hash
- They identify one entry in the network's log, which every device keeps, and each entry names the previous one's hash. Changing what any entry says would change every hash after it.
- Activity names only the signers a change needs, never an extra signature someone added later.
- It never contains keys, invites, reply codes or anything secret: the log holds public keys only, shown as codes and IDs.
- It never says anything about anyone's traffic. It records changes, not connections.
- People's names and email addresses are included, as you or they set them.
Save it as CSV or JSON
- Open Administer, then Activity.
- Choose Save as CSV (for spreadsheets) or Save as JSON (for monitoring tools).
- The whole history is saved in your Downloads folder, and the app says the file's name.
CSV opens in Excel. The file the app saves starts with a byte order mark, so Excel reads names with accents correctly. The command line's CSV has none, for tools that don't expect one.
The formats are stable. Columns and fields are only ever added, at the end, so your spreadsheets and monitoring keep working.
Command line
On Windows, in Terminal (Admin), once you have set $mt and $st. On Linux, in a terminal. Before you start
Write the whole history as CSV, or as JSON, oldest first:
[Console]::OutputEncoding = [Text.Encoding]::UTF8
& $mt audit $st northwind -format csv | Set-Content -Encoding utf8 $HOME\Downloads\northwind-activity.csvsudo multitunnel audit /var/lib/multitunnel northwind -format csv > northwind-activity.csv[Console]::OutputEncoding = [Text.Encoding]::UTF8
& $mt audit $st northwind -format json | Set-Content -Encoding utf8 $HOME\Downloads\northwind-activity.jsonsudo multitunnel audit /var/lib/multitunnel northwind -format json > northwind-activity.jsonOn Windows, the first line keeps names with accents intact on their way into the file. -format text, the default, is for reading in the terminal. -since works with every format.
The file formats
CSV: UTF-8, with a header row. The columns are network_id, seq (the entry's number, from 0), time (RFC 3339, UTC; empty if the entry has none), kind (the log's own name for the change, such as add-device), what (the sentence), by (who made it, in words), by_ids (their key codes or device IDs, separated by spaces) and hash (the entry's SHA-256, in hex). A cell that starts with =, +, -, @, a tab or a carriage return is written with a leading ', so a spreadsheet never runs it as a formula.
JSON: {"format": "multitunnel-audit-1", "network", "networkId", "events": [{"seq", "time", "kind", "what", "by": [{"role", "name", "id"}], "hash"}], "total"}, oldest first. total is the number of changes in the whole history, and role is admin, recovery, device or delegate.
A different layout would get a new format name.
Still stuck?
Email us and a person will reply. For a security problem, write to security@multitunnel.co.uk instead.