Every action Avvi takes is recorded, including the ones that were refused. The record covers who asked, which client it was for, what was targeted, the result, and the address the request came from.

Refusals are recorded as carefully as successes, which is what makes the record useful when somebody says they were blocked and you cannot reproduce it.

The record is filtered rather than browsed. Deciding what you are looking for first is faster than scrolling.

Before you begin

Know roughly what you are looking for: a person, a client, a date, or a kind of event. Any one of those narrows it enough.

Decide whether somebody outside Avvi needs a copy, because that changes the last step.

Find an action

1. Open Logs.
2. In the Filters card, set what you know. User email, Client, Event type, Result, Target, and a Start date and End date are all available.
3. Apply the filters. The list narrows to matching entries.
4. To share the result, select Export CSV or Export JSON.

Filtering by Result is the quickest way to answer whether something succeeded. Success and failed are the two that carry most of the traffic.

Good to know

When a user asks what Avvi did for them, or says a change did not happen, this record answers it without needing their conversation.

Each entry is stamped with how long it is meant to be kept: a year for reads, sign-ins and permission checks, three years for support escalations, and seven for anything that changed something.

A refusal is recorded, but not reliably under the denied filter. Search by the person and the day instead, and read the entries rather than filtering for a refusal.

Verify it worked

Ask Avvi to do something small and read-only, then filter by your own User email and confirm the entry appears.

If it does not, widen the date range before concluding anything is missing.

If something doesn’t look right

If an action you remember is not there, check the date range and the client filter first. Both are common causes of an empty result.

If an export is empty, confirm the filters produced results on screen before exporting. The export follows the filters.

If an entry shows a result you did not expect, read the target and the client on that row before assuming the wrong thing ran.

If none of that explains it, open a support conversation from the Help drawer. Include the date, the client, and the person’s email address.

FAQ

Q: How far back does the record go?

A: It depends on the entry. Changes are kept for seven years, reads and sign-ins for one.

Q: Can I give a client their own record?

A: Filter by that client and export. The export contains only what the filters matched.

Q: Are refused actions recorded?

A: Yes. Find them by filtering on the person and the day rather than on a result.