PYLO Settings: Team and access
Audit log
A read-only record of every change made in your workspace, who made it and whether it went through.
The audit log lists every change made in your workspace, newest first. A change can come from a team member, someone at your agency, an API token, or PYLO itself. Use it to answer questions like who changed a setting, when, and whether the change was accepted.
Who can open it
Only owners and admins. The audit log is not shown in the Settings menu for anyone else, and anyone else who opens the address is sent to Account.
Reading the log
The line under the title says which dates the log covers. Each row has five columns:
| Column | What it shows |
|---|---|
| When | The date and time of the change. |
| Who | The name of whoever made the change, with the kind of actor underneath: Team member, Agency, API token or PYLO. |
| What | A short description of the change, such as the area that was changed. Hover over it to see the exact action recorded. |
| Reason | The reason given for the change, if there was one. Otherwise the pending dash. |
| Result | Done if the change went through, Refused if PYLO turned it down, or Failed if something went wrong. |
Filter the log
- Choose who to show:
Everyone,Team members,Agency,API tokensorPYLO itself. - Optionally set the
FromandTodates. - Optionally type a
Tool, such asclose, to see only changes to that tool. - Optionally choose how the change was made:
By API,By template,In a browserorBy a person. - Optionally paste a
Plan idto see every change one plan made. - Choose
Filter.
Choose Clear to go back to the whole log. If nothing matches, the page says so and suggests clearing the filters.
Export the log
Choose Export CSV to download the rows the filters show, up to 5,000, as a spreadsheet: when, who, the action, what it touched, the plan, who approved it and how, and how it was made. Your agent can read the same with list_audit_events and export_audit_events.
When the log is empty
If no changes were made in the period, you see "No changes in this period". Every change a person or a token makes lands here as it happens. If the audit log is not yet switched on for your workspace, the page says so in place of the table. PYLO switches this on for your workspace.
What changes elsewhere
Nothing. The audit log is read-only, and nothing on this page changes your workspace. To see what a particular token has been doing, compare its name here with the list on API tokens.