Audit Trail
What This Page Covers
Section titled “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
Section titled “How It Works”FSRevs automatically maintains a detailed audit trail for changes to sensitive and important data. Every time a team member creates, updates, deletes, or restores a tracked record, an audit entry is recorded with the exact details of what changed.
Audit tracking is always on and cannot be disabled — it runs silently in the background to ensure accountability.
What’s Logged
Section titled “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 Widgets — Widget 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
- Authentication — Login attempts and sign-in activity
Note Audits and Draft History
Section titled “Note Audits and Draft History”Notes separate shared publication from unpublished recovery:
- Publishing a Note records a canonical 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.
What Each Entry Shows
Section titled “What Each Entry Shows”Every audit entry records:
| Detail | Description |
|---|---|
| Event | The type of change — created, updated, deleted, or restored |
| User | The team member who made the change |
| When | The exact date and time |
| What Changed | The specific fields that were modified, including old and new values |
Viewing the Audit Trail
Section titled “Viewing the Audit Trail”Audit logs are accessible in the portal. You can view audits at the account level or for specific records:
- Account-wide audits — See all changes across your account
- Per-record audits — View the change history for a specific location, user, flow, or other record
- User activity logs — See all actions performed by a specific team member
Two Views Per User
Section titled “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 — A log of all actions that user has performed across the system
Who Can See What
Section titled “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 the customer 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
Section titled “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, so export or otherwise preserve information needed for a long-running investigation.