Audit member directory privacy changes

This guide shows you how to view the full history of directory privacy changes for a member, including changes the member made themselves and changes made by admins.

Who can do this: Admins with the member:view-privacy-audit permission.

Before you start

Every change to a member’s directory privacy settings — whether the member made it or an admin applied it — is recorded automatically in the privacy audit log.
Admin-initiated changes include the admin’s ID. Applying privacy defaults to existing members from the Privacy defaults screen — and undoing it — adds a row for each member it changes; the reason code you chose is kept with that update rather than on each row. (v1.1, 2026-10-17: this said a retroactive apply’s rows “include the reason code and the admin’s ID”.)

Steps

Open the privacy audit log

In the admin sidebar, select Members and open the member record you want to review.
Select the Privacy audit tab on the member’s detail page.
The audit log loads, showing a table of all recorded directory privacy changes for this member.

Read the audit log

Each row in the table shows:

Timestamp — when the change occurred.
Change description — a plain-language description, such as “Opted out of directory listing” or “Set Phone to Members only.”
Policy version — the privacy policy version in effect at the time.
Event source — how the change was made (for example, “Profile edit” means the member changed it themselves).
IP address and User agent — the device details at the time of the change.

Rows where an admin made the change on the member’s behalf also show the admin’s ID. They don’t show a reason: when you apply privacy defaults to existing members, the reason you choose is kept with that update, not on each member’s row. [amended pre-merge 2026-10-17, c21 BD r2: this listed “The ReasonCode label (for example, “Bulk default apply” or “Org policy change”)” — the per-member reason is not built (Story 8.3.5).]

Export the audit log

Select Export CSV to download the audit log for this member.
Your browser saves privacy-audit-<member ID>.csv — every privacy change for this member, newest first — and “Privacy history CSV downloaded” appears. The file has these columns: Timestamp, Event, Category, Note, Source, Policy version, Admin user ID, IP address, User agent, Event ID.
An export holds up to 1,000 rows. If this member has more than 1,000 privacy changes, nothing downloads and you’ll see “This member has more than 1,000 privacy changes — more than one CSV download holds. Nothing was downloaded.” The export never goes to your export history and no email or notification is sent.

Verify

You’ll know the audit log loaded when the table appears with timestamped rows. After exporting, the CSV file is in your browser’s downloads and “Privacy history CSV downloaded” appears.

If something goes wrong

“Could not load privacy history” — select Try again to reload the audit log.
The Privacy audit tab is missing — your admin role may not include the member:view-privacy-audit permission. Contact your organization’s primary admin.
“Could not export privacy history” — the message under it names the exact cause:
- “…your role doesn’t include the “View the directory privacy audit” permission” — your role can’t view or export this log.
- “This member has more than 1,000 privacy changes…” — the log is longer than one export holds; nothing was downloaded.
- “This member no longer exists in your organization…” — the member was removed; there is no history to export.
- “MapleGather could not read this member’s privacy history right now…” — reading the log failed; select Export CSV again.
- “Could not reach MapleGather to export — check your connection…” — your browser couldn’t reach MapleGather; check your connection and select Export CSV again.