The audit log

The audit log is Chandler's record of every change: who did it, what they did, and when. Nobody can edit or delete an entry, not even a license admin.

You need the License admin permission to open it. Click Audit log at the top of the page.

Finding who did what

The newest entries are at the top. Use the filters above the list to narrow it down:

Who: part of a person's email address, for example ada or @exactnet.ai.
What: the kind of action, for example Signed in or Suspended a license.
When: a start date, an end date, or both. Both days are included.

Click Show entries to apply the filters. Click Clear filters to see everything again.

For example, to see everything Ada did last week:

Type ada in Who.
Set From to last Monday and To to last Sunday.
Click Show entries.

Reading an entry

Each row shows:

When: the date and time, in UTC, the world's standard time. Under it, in grey, is how long ago that was.
Who: who did it. Under the name, in grey, is what kind of actor it was:
- Staff: a person, shown by email address.
- Customer install: one of our products at a customer's site.
- Publishing tool: a product's build system, using a publisher token.
- Chandler: Chandler itself.
- Not signed in: someone who tried to sign in and was refused.
What: the action, in plain words. Under it, in grey, is a short code that engineering uses. You can ignore it.
Details: click Show details to see what changed. Before is how things were, and After is how they are now.

Secrets are never stored in the audit log, so you won't see them in the details.

Loading more entries

The list shows 50 entries at a time. Click Load more at the bottom to see older ones.

Exporting the audit log

Set the filters you want. The export uses the same filters as the list.
Click Export to spreadsheet.
Chandler downloads a CSV file that opens in Excel or Google Sheets.

The export holds at most 10,000 entries. If you need more, narrow the dates and export in parts. Exporting is itself recorded in the audit log.

What the actions mean

Signing in and staff

Action	What it means
Signed in	The person signed in to Chandler.
Signed out	The person clicked Sign out.
Confirmed it was them	The person signed in again before an important action.
Was checked again by the sign-in service	About once an hour Chandler asked the sign-in service, without showing a screen, whether the person still has access, and updated their permissions.
Was refused sign-in	Someone tried to sign in without a permission, while disabled, with a guest account, or without a second sign-in step. It is also recorded when the hourly check fails.
Signed a person out everywhere	A license admin used Sign out everywhere.
Disabled a person	A license admin turned someone's access off.
Enabled a person	A license admin turned someone's access back on.
Exported the audit log	Someone downloaded the audit log as a spreadsheet.

Customers, licenses and secret codes

Action	What it means
Added a customer	A license admin added a new customer.
Changed customer details	A license admin changed a customer's name, contact or notes.
Issued a license	A license admin gave a customer a license for a product.
Issued a replacement license	A license admin issued a license in place of a revoked one.
Renewed a license	A license admin gave a license new dates.
Suspended a license	A license admin paused a license. The reason is in the details.
Resumed a license	A license admin ended a pause.
Revoked a license	A license admin ended a license for good. The reason is in the details.
Downloaded a license file	Someone downloaded a license file, usually for an offline install.
Created a credential	A license admin made a new secret code for an install.
Rotated a credential	A license admin replaced a secret code with a new one.
Revoked a credential	A license admin switched a secret code off for good.

The secret codes themselves are never in the audit log.

Releases

Action	What it means
Registered a new release	A build system sent in a new release. It became a draft.
Checked a release's files	Chandler checked a release's files for its build system.
Published a release	A release publisher made a release available to customers.
Withdrew a release	A release publisher took a release back. The reason is in the details.
Put a release back to Files not checked yet	Chandler found that a stored file had changed or gone after it was checked, so it did not publish the release. Check the files again before publishing. The reason is in the details.
Downloaded an offline package	Someone made an offline package of a release for a customer.
Downloaded an offline package's signed description	Someone downloaded the signed description file of an offline package for a customer.
Created a publisher token	A release publisher made a secret code for a build system.
Revoked a publisher token	A release publisher switched a build system's secret code off.