Audit Trail & Undo

Many of the changes made in your agency are recorded, so you can see who changed what and, in most cases, put it back. This page lists which ones.

On the Audit Log page, someone attached to a sub-agency sees the entries about their own sub-agency's records. Entries about records that belong to the whole agency, such as its settings and channels, are not listed there for them. A record's own Audit Log tab still lists that record's entries to anyone who can open the record, but an entry you can't open from the Audit Log page has no View button there.

What is recorded #

• Creating or editing a contact, event, application form, message template, message campaign, compensation plan, monthly statement, sub-agency, role or profile photo template on its own page.
• Editing a host's platform details on their own page.
• Creating, editing and deleting an onboarding sequence on its own pages, with the steps you add, change, reorder or remove there, and deleting sequences from the list. Making a sequence active switches the other active sequence of its sub-agency (or of the whole agency) off in the same entry, so Undo puts the earlier one back on.
• Creating, editing and deleting substatuses on their own pages, and copying a list of them from another platform.
• Changing the status or substatus of several hosts' platform records at once.
• Adding, editing, deleting and restoring compensation tiers.
• Deleting and restoring application forms, from the list (one or several at once) or from the form's page.
• Adding, editing, reordering and deleting an application form's questions on its Questions tab, and deleting several at once. Undoing a deletion brings back the question, and a question shown only for its answers depends on it again.
• Adding, editing and deleting a host's monthly targets.
• Generating statements, marking them paid, and reopening a paid statement.
• Deleting and restoring monthly statements.
• Deleting a sub-agency, on its own edit page or from the list. A sub-agency that still has team members can't be deleted, and a selection that includes one deletes none.
• Removing and restoring event participants.
• Deleting a contact, and restoring them. Restoring brings back what was deleted with them.
• Archiving and un-archiving a contact.
• Sending team invitations. If we can't confirm which plan your agency is on, an entry that would bring an invitation back can't be undone or redone until that is sorted out.
• Changing a team member's access level and permission roles, and removing a member, on the Team page. Once the person has rejoined, their removal can no longer be undone. Nobody can undo or redo an entry that changed their own access level, roles or sub-agencies, and an admin attached to a sub-agency can't undo or redo any change to the team. An entry that would put someone back into a sub-agency that has since been deleted can't be undone or redone.
• Saving Agency Settings or Channels. The WhatsApp and email credentials and the custom domain are not recorded, so Undo never changes them. An entry that changes the email provider or the WhatsApp phone number ID cannot be undone or redone; set the email provider in Agency Settings and the phone number ID in Channels.
• Switching automatic messages off or back on, on the Automatic messages page.
• Finishing the setup wizard. This entry can't be undone; to change a setting afterwards, use Agency Settings (WhatsApp is in Channels). The WhatsApp access token it saves is not recorded. Each team invitation it sends is an entry of its own.
• Adding, editing and deleting a WhatsApp number, and making one the default, on the WhatsApp Numbers page. Its credentials are not recorded, and none of these entries can be undone or redone.
• CSV imports: Import leads (CSV) and the Import … contacts buttons on the contacts list, the import on the events list, and a CSV import in the Documents area. Each import that changes something is one entry. Imported stats, including the record of each report, and stats typed in by hand, are not recorded. Undoing an import that added hosts moves them to deleted records with what goes with them, as Delete does, and Redo brings them back. If anything has been added to or changed on a host it added since (for example an edit, a tag, a statement, a task, a message, points, or access to the host app), the import can't be undone: remove those hosts one by one with Delete on each host's edit page. Only admins who aren't attached to a sub-agency can undo an import that added hosts.
• Accepting an application, on its page or from the applications list. Undo puts the application back to waiting for review. A host the accept added moves to deleted records with what goes with them, as Delete does, and Redo brings them back; on a host you already had, Undo puts back only what the accept changed. If anything has happened since to a host it added, or to a platform account it added, or a detail it filled in on a host you already had has been changed since, the accept can't be undone. Messages its onboarding sent don't stop it, and stay sent. Only admins who aren't attached to a sub-agency can undo an accept that added a host. See Undoing an accept.
• Merging contacts. A merge can't be undone.
• Undoing and redoing an entry.

Changes made anywhere else are not recorded. Some fields are never recorded, passwords among them. Replacing a profile photo template's image is not recorded either.

One-click undo #

An admin can undo most recorded entries with a single action, reverting the record to its prior state.

Undo is available to agency admins. Undo rewrites a record from the history rather than from a form, and it will happily reverse someone else's work — so it sits with the people who answer for the account. Everyone else keeps their normal edit rights and can correct a record forward. If anyone else presses Undo — on the message shown after saving, for example — they see Unable to Undo and nothing changes.

An admin attached to sub-agencies can undo or redo an entry only when every record it changed is in their sub-agencies, and not one that changed which sub-agency a record belongs to.

If part of an entry can't be put back — a record has been changed again since, or was created and cannot be recovered after deletion — the entry's page doesn't offer Undo, and Undo on the message after saving shows Unable to Undo. Usually nothing has changed.

A very large entry is not reversed at all. An entry holding more than 1,000 recorded changes offers neither Undo nor Redo: its page reads "Undo and Redo are offered only for entries of up to 1,000 changes", and names how many that entry holds. An entry of exactly 1,000 is still offered. Most of what reaches that size is bulk work — marking more than 500 monthly statements paid in one run, which records two changes per statement; generating more than 1,000 statements in one run; restoring an event's removed participants in bulk. An undo is itself recorded, as an entry two changes larger than the one it reverses, so undoing an entry just under the limit produces one just over it. Ordinary form saves, single deletes and single restores are nowhere near it.

An undo — or a redo — can also stop partway, if a record changes while it is running. The entry is then left partly reversed, and its page may stop offering Undo or Redo. From the entry's own page you are told when this happens. From the message shown after saving, it reads Unable to Undo, so treat that message as "check the record" rather than as a promise that nothing was written.

When other work keeps changing the same records, an undo or redo may be finished in the background instead. The entry then shows Undo in progress (or Redo in progress) on its page and in the History list. When it ends you normally get a notification saying how, such as Undo finished, Undo finished, in part, Unable to Undo or Undo didn't finish (for a redo, the same with Redo). If you don't get one, open the entry to see where things stand. It runs as you, with the permission you have when it runs.

Nobody can edit an entry. Entries are removed when a host's data is erased, which takes that host's history with it, and when the agency's account is deleted.

Deleted records #

Most records are kept behind the scenes when deleted, so they can be recovered. Some are not, and deleting one of those is permanent. A deleted stat row is kept behind the scenes and included in your full data export, but it can't be restored from the app.