> ## Documentation Index
> Fetch the complete documentation index at: https://docs.forepost.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Team briefings

> Subscribe teammates to the Daily Brief and Weekly Watch on their own email.

For most of Forepost's history, the Daily Brief and Weekly Watch went only to the workspace **owner**. That made sense for a single CX leader; it doesn't make sense for a four-person team.

**Team briefings** lets owners and admins subscribe any teammate to brief delivery on their own email. Members can self-manage their own subscription.

## What you can configure per teammate

<CardGroup cols={2}>
  <Card title="Email" icon="envelope">
    Must match a verified workspace member.
  </Card>

  <Card title="Cadence toggles" icon="toggle-on">
    Daily Brief on/off · Weekly Watch on/off, independently.
  </Card>

  <Card title="Scope" icon="filter">
    `full` (everything the owner sees) or `department` (their agents only).
  </Card>

  <Card title="Self-managed" icon="user">
    Members can always unsubscribe themselves, even if the owner subscribed them.
  </Card>
</CardGroup>

## Two scopes, two reads

The team-level numbers (CSAT, volume, FRT, deflection, capacity, etc.) are unchanged regardless of scope — they're org-wide signals. What `scope: 'department'` changes:

| Block              | Full scope | Department scope         |
| ------------------ | ---------- | ------------------------ |
| Eight signals      | ✓          | ✓                        |
| Per-agent context  | All agents | Member's department only |
| Worst-CSAT samples | ✓          | —                        |
| Active decisions   | ✓          | —                        |
| Recent actions     | ✓          | —                        |

A Tier-2 lead doesn't need the executive view. A department head wants their team's numbers, not the whole org's.

## Where to configure

Settings → Delivery → **Team briefings**. Owners and admins add new rows; members can flip their own toggles or unsubscribe themselves.

## Delivery cadence

Members ride the **owner's schedule** — same timezone, same local hour. Forepost doesn't yet store a per-member tz/hour; teams running the same business hours don't notice, and the alternative added settings surface for little real gain. If you need per-member timezones, [tell us](mailto:kian@forepost.ai).

Daily briefs send Monday-to-Friday at the owner's chosen hour. Weekly Watch fires on Monday morning local. Dedup is per-row via `member_brief_subs.daily_last_sent` and `weekly_last_sent` so a missed cron tick doesn't double-send.

## API

```bash theme={null}
GET    /member-briefs                       # list (members see only their own)
POST   /member-briefs                       # upsert — body { email, dailyBrief?, weeklyWatch?, scope? }
DELETE /member-briefs?email=...             # unsubscribe
```

## Email patterns

The Resend integration that handles the owner's brief is reused for member subscriptions. Same from-address. The unsubscribe link in the footer respects the member's row, not the owner's, so a member clicking unsubscribe doesn't accidentally turn off the owner's delivery.

## What it isn't

* **Not a redistribution list.** Each subscription is scoped to one verified member. You can't subscribe `team-cx@company.com` and have it fan out.
* **Not an admin override.** Members can always unsubscribe themselves, even if the owner added them.

## Privacy

Subscriptions live in your workspace's D1 scope. Email addresses must verify through Clerk before any brief is sent (same posture as the owner). The unsubscribe link is HMAC-signed.