Analytics · Schedule
Route /analytics/scheduled-reports Flag scheduledReportsEnabled

Scheduled Reports

Cadence and recipients for saved report definitions — delivery config, not a new metric store.

Scroll to Flowcharts. Scenario: Schedule a saved analytics report.

Cadence

When a saved report leaves the building

Scheduled reports attaches cadence and recipients to definitions you already saved. It does not store a new set of numbers.

Analytics → Scheduled reports Route /analytics/scheduled-reports Org flag scheduledReportsEnabled Executive · Finance · HR · Admin

The job of this console

Pick a definition, set who and when, save. Every send still respects persona masking.

Seat at the table

Executives, finance, HR, admins with scheduledReportsEnabled. Recipients must already be allowed to see the grain.

The working rhythm

Create or edit a schedule, verify a test send, leave it running, audit failures.

Moments that bring you here

Monday pack automation. Month-close appendix. Replacing a manual export. After a builder save.

ⓘ
Delivery config
Admin jobs is platform cron. This page is report cadence. Masking is not optional on the email.

Flowcharts

1 — Cadence on a definition

Attach a schedule to a saved report, not to a one-off screenshot.

flowchart TD
  A[Open Scheduled reports] --> B[Pick definition]
  B --> C[Cadence / recipients]
  C --> D[Save]
  D --> E[Sends with masking]
            
  1. 1
    OpenAnalytics → Scheduled reports.
  2. 2
    PickA saved definition.
  3. 3
    CadenceRecipients with grants.
  4. 4
    SendStill masked.

Overview

Scheduled reports is workflow on report definitions. Admin scheduled jobs is platform cron. Recipients still receive persona-masked output. This table is not a warehouse.

How to use

1. No grant, no recipient
Scheduling is not an access bypass.
2. Definition first
Build on Report builder.
3. Payroll/medical
Prefer not to schedule unscoped pay packs.