Audit Logs for Enterprise admins: Track team membership and join request activity

Last updated: November 20, 2026

Available on: Web — the admin portal. There is no Audit Logs page in the desktop or mobile apps.

Audit Logs shows who changed membership, seats, roles, invitations, or join requests in your enterprise, so you can filter the matching records and export them.


Open Audit Logs

Audit Logs requires an enterprise Admin, SuperAdmin, or IT Admin role and shows only your organization's records. Non-admins are redirected home or see “You are not authorized to access this page”.

  1. Open the admin portal.

  2. Select Audit Logs, then Events if both views are available.

Note: Events appears only when it is enabled for your enterprise; Audit Logs stays available to admins either way. If neither is available, “Audit logs aren't available for your enterprise yet.” appears.


Filter the records

Control

Behavior

Date range

Defaults to the last 30 days; choose 7-, 30-, or 90-day presets or custom dates.

Event types

Select individual types, whole categories, or Select all / Clear all.

Page size

Choose 20 (default), 50, or 100 events; use Load more for additional pages.

Refresh

Reloads the first page and drops pages opened with Load more.

Every organization sees the same filter list: Membership for Member added, Member removed, Member role changed, Member invited, Invitation resent, and Invitation revoked; Seats for Seat changed; Join requests for approvals and rejections.

Select both dates, with the start on or before the end and a range shorter than 92 days; future dates aren't selectable. Invalid dates stop automatic loading and disable exports, but not Refresh. Selecting no event types disables the table, Refresh, and exports; select at least one type to restore them. “No events found for this range.” means no records match your filters.

Changing dates, event types, or page size restarts pagination. Refreshing moves preset ranges forward to today and leaves custom ranges unchanged.


Interpret the records

The table and CSV have six columns: Timestamp, Actor, Action, Target, Details, and Event ID. Actor identifies who acted and Target the affected person, organization, or resource; automatic actions show a service actor rather than a named admin. Names stay as recorded when the event occurred; a missing name falls back to an ID, then to an em dash in the table or a blank CSV cell. There are no separate email-address fields.

Details shows the setting and previous → new value for organization-settings changes, or old → new role for role changes. Other actions show an em dash, or a blank Details cell in CSV.

  • Seat changes: Changing a member's seat from the members table records Seat changed, shown in the Action column as “changed member seat” — separate from “changed member role”. Details shows the previous → new seat, for example “Full seat → Dictation only”, or “No seat → Full seat” when the member had no seat before; an unrecognized seat value appears exactly as recorded, in the table and the CSV export. Each affected member gets its own event; rejected and no-change requests record nothing, and a repeated request is recorded once.

  • Bulk updates: Updating seat type, role, or department for several selected members at once records one event per member and per changed field, once you save. Members whose values couldn't be changed, and fields left as they were, record nothing.

  • Invitations: Member invited is recorded after the invitation email sends. Invitation resent is recorded when an admin resends a pending or failed invite from the Team page; if a Wispr support admin resends for you, that Wispr admin is the actor while the invitation keeps its original inviter. Revoking an already-revoked invitation records nothing, and automatic domain joins that create an invitation can record Member invited instead of Member added.

  • Join requests: Individual and bulk approvals record both Join request approved and Member added for each accepted user; declines record Join request rejected. A bulk-approval entry that cannot be added is treated as rejected, with no approval or member-added event.

  • Directory removals: Removals from directory sync show a service actor. A removal that would leave no administrator or no billable user is refused and records no Member removed event.

  • Membership policy: Changes to auto-invite or disable team trial record Membership policy changed; saving an unchanged value records nothing. Moving a member to another department is recorded for that member.


Export results

  1. Set the date range and event types you need.

  2. Select Export CSV or Export JSON.

Exports cover the whole filtered range, not just loaded rows, up to about 10,000 events regardless of page size. JSON contains full event records; CSV uses the six columns above. Downloads are named audit-events-<start>_to_<end>.csv or .json with yyyy-MM-dd dates, and completion confirms the exported count — an empty range downloads a header-only CSV or empty JSON array.

Important: Narrow the date range and retry when an export reaches its limit. If an export fails, select the export button again; the error may say “Failed to export audit events. Please try again.” or give a more specific message.


If events aren't available

Events is enabled but not set up

Events stays visible with exports disabled, and the setup message depends on your domain status:

  • No linked domains: Contact enterprise@wispr.ai to add one.

  • Unverified domain: Check status under Settings → Organization and contact enterprise@wispr.ai for help; Wispr completes verification.

  • Setup pending: Contact enterprise@wispr.ai if this persists.

The event list won't load

With event types selected, a loading failure before any rows load replaces the filters, Refresh, and exports with View audit events; this does not apply to the setup state above. Failed refreshes or Load more attempts leave already-loaded rows and controls visible.

  1. Select View audit events to open your organization's events in a new browser tab.

If “Couldn’t open the events viewer. Please try again.” appears, select it again; the message can also mean the request to open the viewer failed, not only that the window was blocked or closed.


Still need help?

  • Missing Events access: Contact your account team.

  • Streaming audit events to a SIEM: Requires an Enterprise plan and streaming access; contact Wispr support to enable it or if a streaming-failure banner persists.

  • Repeated loading or export failures: Contact support with your enterprise, browser and device, the error message, and the steps you tried.