Export · reporting

Export region report — core practice

Generate a report of your scope’s ROOT / PACE / THRIVE picture. Privacy rules are applied automatically — sentiment exports aggregate-only, never by name.

Scope — export anything you can view, at any level you can view it

Whole orgCore Practice

Narrow to team

🔒 Only scopes you’re entitled to are listed; every selection is re-validated server-side — a hand-edited scope is rejected.

Include lenses

✓ = included · struck-through = excluded

Filter · role / tag

Role and tag filters apply at team scope (they’re person-level). This is an aggregate report.

Time-box

Report-period label only — figures reflect the current measured period (§8 — historical slicing arrives with Chunk 9 mapped hours). The picker names the window, it does not filter history.

Comma-separate multiple recipients. We email a link to the gated report — each person opens it scoped to their own access.

What this export will contain

Resolved from your role + scope — the same rules as on-screen. Updates as you change the controls.

Sentiment (THRIVE) — team aggregate only. Never attributed to an individual.
ROOT / PACE per team + the scope roll-up.
k-anonymity floor (4): sub-floor cohorts have sentiment suppressed (none currently in this scope).
Evaluative tags excluded (Flight-risk-watch, High-potential) — never in an export.
Out-of-scope regions — not exportable at your scope.

The serializers render this resolved model — they never re-query data — so an export cannot reach anything the screen wouldn’t show you.