Set up configurable agent briefs
Configurable briefs let you schedule saved, dated reports from Operations and Business agents. Each brief captures evidence, applies explicit coverage limits and delivers the output to chosen recipients — replacing the earlier fixed morning digest. ## Before you begin - You must be a workspace owner or administrator. - The agent must already be created in your workspace. - Decide the schedule, evidence scope, sections and recipients before configuring. If you currently use a **legacy morning digest**, see [Convert a legacy morning digest](#convert-a-legacy-morning-digest) below before creating a new brief. ## Configure a brief 1. Open the agent’s editor in **Agents**. 2. Select the **Brief** tab. 3. Choose a **schedule**: - **Weekdays** — runs Monday–Friday. - **Weekly** — runs on a chosen day. - **Monthly** — runs on a chosen date. 4. Set the **timezone**. Hub applies daylight saving adjustments automatically; UTC is preserved for existing workflow schedules. 5. Set the **reporting period** — the window of activity or records the brief should cover. 6. Under **Evidence**, select the **collections, shared views or custom filters** that bound what the agent can read. The brief uses read-only access; it has no write tools during a brief run. 7. Add or remove **sections** to control what the brief includes (for example, summary, highlights, risks, recommendations). 8. Set **recipients** — workspace members who can open the saved report from their Activity digest without gaining general agent-history access. 9. Optionally set a **Slack destination** to deliver the brief summary to a connected channel. 10. Save the brief settings. ## What a brief contains Each saved brief includes: - Dated evidence references with query counts. - Explicit coverage limits (what the agent read, what it excluded). - The sections you configured. - A link to the full saved report in the agent’s run history. Briefs appear in the agent’s **Run history** alongside other run types. ## Delivery Brief delivery uses the same infrastructure as agent run notifications: - In-app delivery appears in each recipient’s **Activity** feed. - Slack delivery uses a shared outbox with deduplication and bounded retry. - Delivery status and retries are tracked independently of the brief generation itself. - Delivery respects each recipient’s personal automation-alert preferences. ## Use a brief in a workflow A workflow **Run agent** step can trigger a brief run and wait for it to complete. Named step outputs expose: - `{{agent.summary}}` — the brief’s summary text. - `{{agent.brief}}` — the full brief content. - `{{agent.reportUrl}}` — a link to the saved report. These outputs can be used by later actions in the same workflow, such as sending a Slack message or updating a record. Administrator publication of the workflow binds the full graph to server-owned authorisation. ## Convert a legacy morning digest If your workspace uses a **legacy morning digest**, Hub provides an explicit, atomic conversion in **Workspace settings**: 1. Open **Settings → Workspace**. 2. Find **Morning digest** and select **Convert to brief**. 3. Review the pre-filled settings — Hub preserves your old enabled state, 08:00 UTC time, 24-hour reporting period and personal notification preferences. 4. Select which **collections** the brief should use. This step is required before the conversion completes. 5. Confirm the conversion. The conversion is atomic — it avoids overlap with an active legacy send. The old digest is disabled as part of the conversion. No production migration is run automatically. ## Coverage limits To keep briefs predictable and auditable, Hub applies explicit limits during generation: - Only the collections and filters you selected are read. - Query counts are recorded in the saved brief. - The agent cannot write records, apply site changes or submit code PRs during a brief run. - Snapshot writes reject content over 750 KB without truncation. These limits are shown in each saved brief so recipients know exactly what the agent covered.