These reports can be found on the "All Reports" page under the "System" tab.
🧾 Audit Log
Also known as "Audit Report"
Click the arrow to learn more
Click the arrow to learn more
📣 Want to dig deeper into how the Audit Log works?
Check out our full Help Center article for a detailed breakdown of fields, filters, and tips on how to trace specific changes in the system.
📋 What
The Audit Report logs a complete history of changes made in the system, whether by users or background processes. It provides visibility into data updates, such as roster adds/drops, edits to customer information, or program modifications. Each entry includes the action, affected ID, old and new values, who made the change, and when it occurred.
🔑 Key features
Filter by:
View Changes To: Everything, Customers, Rosters, Programs, and more
Customer ID / User ID / Roster ID: Focus on one specific entity
Edited By User: View changes made by a specific employee
Start & End Date and Time: Limit the report to a specific timeframe
Limit: Choose how many results to display at once
Each result displays:
Action performed (e.g., ROSTER_ADD, UPDATE)
Affected object ID and name
Type and field modified
Old and new values
Employee or system that made the change
Timestamp of change
IP address and request metadata
Export options: CSV or PDF
✅ When to use it
Use this report when you need to audit data changes across the system—such as investigating who edited a customer profile, when a roster adjustment was made, or whether user permissions were updated. It’s especially valuable for administrators, customer support teams, and data compliance reviews.
💡 Pro Tips
If you're trying to trace down a specific change, enter the Customer ID or Roster ID directly to limit noise. Filtering by Edited By User helps hold staff accountable or clarify internal questions about updates. Leave the date fields blank to see a full history. Export a PDF version when changes need to be documented or shared outside the system.
✍️ Electronic Signature Requests Report
Also known as "Digital Signature Report"
Click the arrow to learn more
Click the arrow to learn more
📋 What
The Electronic Signature Requests Report displays all e-signature requests sent to customers, allowing you to monitor their status, review details, and troubleshoot issues. Each request is tied to a booking or customer record and includes submission status, timestamps, and error messages (if applicable).
🔑 Key features
Filter by:
Created After / Created Before (optional date range)
Creator (employee who initiated the request)
Object Type (choose between
BookingorCustomer)
Each result includes:
ID: Internal request ID
Employee: Who created the request
Object – ID: Booking or Customer ID (clickable to view record)
Status: Sent, Complete, or Canceled
Created / Modified Timestamps
Request ID: External reference ID
Error Message (if the request failed)
Export options: CSV or PDF
✅ When to use it
Use this report to check which customers have completed required signatures, troubleshoot failed requests, or confirm when a waiver or document was sent. It's helpful for staff managing waivers, program agreements, or any form requiring a digital signature.
💡 Pro Tips
If you're looking to verify completion for a specific person or booking, enter their Object ID or use the Creator filter. Requests with a "Request Complete" status indicate a successful submission. Export the report to CSV to follow up with customers who haven’t completed their forms. Use the Request ID to trace issues with your e-signature provider if needed.
📬 Email Bounce Report
Click the arrow to learn more
Click the arrow to learn more
📋 What
The Email Bounce Report displays emails that failed to reach customer mailboxes, allowing you to investigate delivery issues and identify addresses that should be removed from your mailing list. Data is retained for the past 30 days.
When you send an email to a customer, the receiving server may reject it for various reasons: an invalid address, a full mailbox, or a temporary network issue. A bounce occurs when that email fails to deliver. This report lets you see which emails bounced, why they bounced, and when. Understanding bounce types helps you maintain sender reputation and follow up with customers effectively.
🔑 Key features
Filter by:
Search - Enter a term to match against bounce error details
Email - Search for bounces tied to a specific email address
Bounce Type - Filter by Permanent, Transient, or Unknown (see details below)
Start Date & Time - Choose when to begin reviewing bounces
End Date & Time - Choose when to stop reviewing bounces
Each result includes:
Received - Date and time when the bounce occurred
Company - The company associated with the bounce
Bounce Code - Internal reference code for the bounce
Bounce Type - Permanent, Transient, or Unknown
SES Message ID - Email service message identifier (SES = Simple Email Service)
Customers - Customer record associated with the email
Emails - The email address that bounced
Raw Bounce - Full JSON data from the bounce (searchable via the Search filter)
Export options: CSV or PDF
Understanding Bounce Types:
Permanent means the email address is invalid, the domain doesn't exist, or the receiving server has actively blocked messages. The recipient will never receive future emails. Dash automatically flags these addresses to protect sender reputation and won't attempt to send to them again.
Transient (also called a "soft bounce") describes a temporary delivery issue, such as a full mailbox or a server temporarily unavailable. The email system will automatically attempt redelivery over several days. If redelivery fails, the bounce becomes permanent. Dash marks the address as temporarily bounced, so future emails can still be sent.
Unknown occurs when the receiving server returned an unexpected or unclear response that couldn't be categorized. These are typically treated as soft bounces, and the system will automatically attempt redelivery.
✅ When to use it
Use this report when a customer reports they didn't receive an important email (invoice, confirmation, waiver link). It's also useful when you need to verify that an email address is valid before sending critical communications, troubleshoot why automated emails aren't reaching customers, or identify addresses that should be removed from your mailing list due to permanent bounces.
💡 Pro Tips
If a customer says they didn't get an email, search by their email address in the Emails column and review the bounce details to confirm whether the address is the issue. Permanent bounces should be investigated. Ask the customer to provide a corrected email address before resending. If you see many Transient bounces for the same address over time, the address may be inactive or abandoned. The Search field is useful for power users: you can enter specific error codes or keywords from the Raw Bounce JSON field to find related issues and spot patterns across multiple bounces.
📧 Email History
Click the arrow to learn more
Click the arrow to learn more
📋 What
The Email History Report shows messages sent from the system to customers, including whether an email has been sent or is still queued for delivery. It provides visibility into the timing, subject, and origin (source) of each email, making it easy to troubleshoot communication or confirm delivery.
🔑 Key features
Filter by:
Customer or Email Address
Source (which part of Dash triggered the message — e.g., Invoice, Registration, Waiver)
Date Range: Start Date & Time, End Date & Time
Optional checkbox: Include Messages Waiting to be Sent
Results include:
Message ID (clickable for details)
Recipient (To) and Sender (From)
Subject
Source (Invoice, File Upload Review, etc.)
Type (usually email)
Status:
sent,queued, orerrorPriority: High or Normal
Employee who initiated the email
Timestamps for when the message was added and when it was sent
Export options: CSV or PDF
✅ When to use it
Use this report to verify email delivery, track outgoing communication for customer support, or audit specific messages (e.g., waiver confirmations, registration notices, receipts).
💡 Pro Tips
Use the "Added" column to see when an email was queued and the "Sent" column to confirm the exact time it was delivered. If you’re troubleshooting missing communication, this timestamp comparison is a great place to start. Filtering by "Source" helps isolate specific types of messages—like invoices, signed waivers, or registration receipts—so you can quickly review what was triggered and when. Searching by a customer’s name or email will give you a full timeline of messages sent to them, which is especially helpful for support or follow-up. If you notice delays, checking the "Include Messages Waiting to be Sent" option will show you emails still in queue. Keep in mind that emails listed with "dash" under the employee column were generated automatically through online customer actions.
🧭 Online Events
Also known as "Customer Events"
Click the arrow to learn more
Click the arrow to learn more
📋 What
The Customer Events report (sometimes referred to as the “Online Events” report) displays system activity tied to individual customers. You can see when a customer logs in or out, attempts payment, signs up for a team, or scans into the facility. Each event is timestamped and associated with a customer record.
🔑 Key features
Filter by:
Specific Customer (or leave blank to view all)
Event Type: Login, Logout, Login Failed, Payment, Payment Failed, Team Message, Signup Request, Signup Accept, Signup Reject, Invite Sent, Track Source, Register, Check-in
Start and End Date/Time
Pre-defined Date Ranges
Display Limit (defaults to 1000)
Results include:
Event Type
Date and Time
Customer Name (clickable for profile access)
Exportable as CSV or PDF for tracking and analysis.
✅ When to use it
Use this report when troubleshooting customer access issues, verifying attendance or check-in activity, or confirming whether customers are engaging with your online portal. It’s also helpful for marketing teams looking to track engagement via Signup or Invite events, and for front desk staff confirming login behavior for recent inquiries.
💡 Pro Tips
Use the Event Type filter to quickly isolate logins, failed payment attempts, or other key customer behaviors. Leaving the customer name field blank allows you to spot trends across your full user base, especially after a campaign or major program release. If you’re monitoring traffic from a specific promo, look for “Track Source” events tied to a campaign ID. For smaller windows of time, reduce the display limit for quicker results, and export to CSV if you need to sort by time, name, or event.
🧠 System Events
Click the arrow to learn more
Click the arrow to learn more
📋 What
The System Events report logs activity performed by your internal users (employees), allowing you to audit events like mass emails, data exports, and system access. Each event record includes the user, timestamp, action type, and system details.
Available system event types:
Team/Class/Camp Email
Customer Broadcast Emails
Customer Data Export
Employee Login / Logout
Login Enabled/Disabled
Login Failures
Data Gateway Access / Failures
Cash Drawer Access
Sticker/Label Printed
Restaurant Order Processed
🔑 Key features
Filter by:
System Event Type (required)
Date and Time Range
Employee Name
Search Bar for specific terms or keywords
Exportable as CSV or PDF
Each result includes:
Event ID
Event Code
Date and Time
Employee (clickable)
Description (e.g., email subject, system path)
IP Address
Details link for further drill-down
✅ When to use it
Use this report when you need to verify which employee sent a broadcast email, exported customer data, or logged into the system during a specific time period. It’s especially useful for auditing employee actions or confirming delivery of communications like team updates or class schedules.
💡 Pro Tips
If you're auditing mass communication, start by filtering for “Customer Broadcast Emails” or “Team/Class/Camp Emails.” Click "View details/email contents" to confirm what was sent and when. Use “Employee Login Failure” to investigate potential access issues. Export logs to CSV if you need to perform deeper analysis or share records with leadership or support teams.






