Pinned Audits
Pinned audits are completed runs that you have marked as important. Pin a run to give it a descriptive name and identify it as a key reference for your governance work.
When to Pin
Pin a run when it serves as:
- A cleanup reference — An audit that informed a recent field cleanup or consolidation decision.
- A governance checkpoint — An audit taken before a major project, policy, or system change, useful for later comparison.
- A migration baseline — An audit that documented the state before a migration, upgrade, or major organizational change.
- A compliance record — An audit that supports regulatory review, audit procedures, or compliance documentation.
How to Pin
Pinning requires a descriptive name. When you pin, you assign a name that helps you remember why the run matters.
To pin a run:
- Find the run in Run History.
- Click the Pin icon (outline pin symbol) in the Actions column.
- A modal appears asking for a run name.
- Enter a descriptive name (up to 255 characters) — for example, "Q4 cleanup approved" or "Pre-migration baseline".
- Click Pin to save.
The run is now pinned and marked with a filled pin icon. Pinned runs remain pinned even if you move them to trash and restore them.
Find Pinned Runs
In Run History, toggle the Pinned filter to show only your pinned runs. This gives you a quick view of your governance references without other clutter.
Unpin a Run
If a run no longer needs to be marked as a key reference, you can unpin it.
To unpin a run:
- Find the pinned run in Run History.
- Click the Unpin icon (filled pin symbol) in the Actions column.
The run remains in Run History but is no longer pinned. The run name you assigned when pinning is preserved.
What Pinning Does Not Do
- Pinning does not change audit results or rerun the audit.
- Pinning does not prevent you from moving a pinned run to trash if you no longer need it.
- If you restore a trashed run, its pinned state and assigned name are preserved exactly as they were.