Audit Trail

What This Page Covers

How the FSRevs audit trail works — a detailed record of who created, updated, or deleted important settings and information across your account.

How It Works

FSRevs records tracked changes such as creating, updating, deleting, or restoring a record. An audit helps answer who changed a setting and what its previous value was.

You do not need to enable audit tracking for each record. Audits cover tracked fields and events; they are not a recording of every page view, keystroke, or customer action.

What’s Logged

The audit trail keeps records for changes to important settings and information across your account, including but not limited to:

• Locations — Creating, editing, or deleting locations and their settings
• Users & Roles — Adding or removing team members, changing roles or permissions
• Review Flows — Creating or modifying flow configurations and settings
• Flow Records — Changes to individual customer responses and review records
• Custom Forms — Creating or editing form configurations
• Branding — Logo, color, and appearance changes
• Review Showcases — Showcase configuration changes
• Review Sites — Adding, editing, or removing linked review sites
• Notes — Workspace notes and team activity
• Customers — Customer record modifications
• Public Pages — Page content and settings changes

Account sign-in activity appears in user Activity Logs. For customer request visits, delivery updates, and review-site clicks, use the response’s Activity Logs. These answer different questions from an audit of edited fields.

Note Audits and Draft History

Notes separate shared publication from unpublished recovery:

• Publishing a Note records a shared saved version and an audit event.
• Changes to title and other tracked metadata, categories, followers, audience or scope, deletion, and restoration create focused audit records.
• Automatic account backups and browser-only recovery drafts do not create audit entries because they have not been published to the shared Note.
• The Note body is preserved in its saved-version History rather than duplicated into ordinary field-level audit values.

This distinction lets an editor recover unfinished work without making it appear that the shared Note changed before Save Note was selected. See Notes for the editor workflow.

Note access and audit access are different

Permission to read a Note does not automatically grant access to its detailed audit page. Note audits require workspace-wide management authority, such as a System owner or Administrator account.

What Each Entry Shows

Depending on the event, an audit entry can show:

Detail	Description
Event	The type of change — created, updated, deleted, or restored
User	The responsible team member when the change has an identified user
When	The exact date and time
What Changed	The specific fields that were modified, including old and new values

Tip

The audit trail shows field-level changes — so if someone updates a review flow’s name, you’ll see exactly what the name was before and what it was changed to.

Viewing the Audit Trail

Open the location, user, Flow, response, or other tracked record and look for its Audits page or action. Availability depends on the resource and your responsibilities.

1. Find the record whose value or state changed.
2. Open its available audit page.
3. Locate the relevant event and timestamp.
4. Compare the recorded old and new values with the current record.

Use Users > Activity Logs when investigating activity attributed to a team member. For customer messages or a customer’s progress through a Flow, start from that response’s workspace instead.

Two Views Per User

Each user has two audit perspectives:

• Changes to them — A record of all changes made to that user’s account (role changes, profile updates, etc.)
• Changes by them — Recorded activity attributed to that user

Who Can See What

Every user can view their own account activity. Viewing another person’s Activity Logs depends on whether you are allowed to manage that account:

• Owners and Administrators can review team-member accounts within their business-wide authority.
• A Location manager can review another user only when that entire account falls within locations the manager controls.
• A shared user’s protected profile and activity remain unavailable when the person also has responsibilities outside the manager’s locations.

Open Users, select the person, then choose Activity Logs when that action is available. Record-specific audit pages follow their own resource and location permissions.

Retention

FSRevs keeps a bounded audit history for each tracked record. Older entries can be removed as newer activity exceeds that record’s retention threshold. For an investigation, promptly record the record identifier, relevant dates, and visible old/new values; contact FSRevs if you need help preserving the available evidence.

If an Expected Change Is Missing

Confirm that you opened the correct record and the correct history type. A notification, a customer click, a published Note version, and a profile-field change can appear in different histories. Older entries may also have left the retained history. A missing audit entry is not proof that an action never happened.

Related Pages

• Roles & Permissions
• Managing Users
• Notes