Daily Sync Report

Reports contains the email and PDF snapshots generated for your organization. Each row shows the report date, report window, movement summary, and delivery status. Check the organization, source provider, timezone, and reporting window before interpreting the results. The Daily Sync Report summarizes the runs recorded in that window. It is not a live view of the current provider records.

​

Read the Report

1. Check the run and attention counts, then the Added, Updated, Removed, Failed, review, and Skipped totals.
2. Read Needs Attention for affected people or records, an explanation, and the recommended next step.
3. Use Sync Coverage to compare changes, attention, skipped records, and run status across sync types.
4. Read the overall takeaway, then expand What Changed for recorded changes grouped by sync type.

• Changes counts records added, updated, or removed.
• Attention counts failures and items that need review. Attention is not included in the change count.
• Sync Coverage shows the sync types represented in the report window.

The six sync types are Groups, Sites, Users, User Fields, Group Memberships, and Site Memberships. Only the types represented in the reporting window appear. Change sections open by default and can be collapsed. Attention is shown separately from routine changes so it is easy to find on a busy day.

​

Names, Fields, and Explanations

The report uses readable names, email addresses, and field labels when available. Internal record IDs and raw provider API responses are not part of the client-facing detail. If the saved report lacks a usable name or explanation, it shows a neutral fallback instead of exposing a technical identifier or inventing information. Reports, sync items, and Review Items use the same client-facing message conventions. Follow the recommended action, then use Run History and Review Items to investigate and verify a correction.

​

Email, PDF, and Online Access

The branded email has the subject Daily Sync Report, a PDF attachment, and a View Report link. The organization and reporting date appear inside the message. The PDF uses the same title, attention-first structure, coverage summary, and grouped changes as the online report. The online report link requires sign-in and access to the organization. Receiving an email does not grant dashboard access. Ask your organization administrator or Bravas contact if you need an invitation. Choose PDF in the report to download it when that action is available. Downloads of saved reports use the current layout and their stored report data; they do not fetch a new snapshot from the source provider. A PDF already attached to an older email does not change retroactively. Organization administrators can use Send Now or Resend where available. These actions send messages, so confirm the recipients and reporting window first. Resend uses the saved report data and the recipients recorded on that report, not a new sync or a refreshed recipient list.

​

Reporting Windows and Detail Limits

Scheduled reports cover the previous local day after that day closes. A scheduled report is not generated when no completed or failed runs fall in its window. For a manual report, check the selected window rather than assuming it covers a full day. The report window includes completed and failed runs that finished within the stated organization-timezone window. A sync type can include movement from more than one run in that window, so use Sync history when you need the full run-by-run audit trail. Report preparation reads up to 80 reportable item rows from each included run and lists up to 40 detail rows in each provider-and-sync-type section. When a limit is reached, the page and PDF show a notice. Summary counts still cover the included runs, while Sync history contains the remaining record detail. Skipped records contribute to the skipped count but are not listed as detail rows.

​

Delivery Statuses

​

Result Meanings

The summary also separates Added, Updated, Removed, Needs Review, Failed, and Skipped counts. A report marked Sent can still contain Needs Review or Failed results.

​

Slack Summaries

When a summary is shared to the configured Slack channel:

• No runs recorded means no runs were included, which can occur for a manually selected window.
• Needs review means at least one failed record or warning was included. The summary gives the failed and warning counts.
• No attention items means no failed records or warnings were included. This is not a guarantee that all source and destination data is identical.

The summary includes the Daily Sync Report title, date, total changes, included runs, PDF, and online report link.