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

# Heads Up: Company-Wide Announcements with Read Receipts

> Broadcast critical updates, safety alerts, and policy changes to your entire organization using Supa Heads Up — with mandatory read confirmations.

Supa Heads Up is a broadcast announcement tool built for organizations where you need to know — not just hope — that every team member has seen an important message. Unlike general chat, Heads Up requires workers to actively acknowledge each announcement before they can dismiss it. This page explains how to send announcements, target specific audiences, and track who has and hasn't read your message.

## Key capabilities

<AccordionGroup>
  <Accordion title="Audience targeting">
    Send an announcement to your entire organization, or narrow the audience to specific locations, departments, or roles. A safety alert at one warehouse doesn't need to interrupt teams at unaffected sites.
  </Accordion>

  <Accordion title="Message types">
    Include text, images, video, and file attachments in any announcement. Use video for product demos or safety briefings where written text isn't enough.
  </Accordion>

  <Accordion title="Read receipts">
    The read receipt dashboard shows a live list of exactly who has opened the announcement and who hasn't. Filter by location or team to follow up with specific groups.
  </Accordion>

  <Accordion title="Mandatory acknowledgment">
    Require team members to tap **I understand** before they can dismiss the announcement. This creates an explicit confirmation record rather than an implicit "probably saw it."
  </Accordion>

  <Accordion title="Scheduled delivery">
    Write the announcement now and schedule it to send at a specific date and time — useful for policy rollouts aligned with a training session or shift start.
  </Accordion>

  <Accordion title="Priority levels">
    Set an announcement to **Standard** or **Urgent**. Urgent announcements appear as a banner notification that persists until the worker acknowledges it.
  </Accordion>

  <Accordion title="Expiry">
    Set an expiry date after which the announcement is automatically archived. Workers who haven't read it by the expiry date are flagged as non-acknowledged in the audit record.
  </Accordion>
</AccordionGroup>

## Sending a Heads Up

<Steps>
  <Step title="Open Heads Up">
    Log in to the Supa web dashboard and navigate to **Heads Up** in the left sidebar.
  </Step>

  <Step title="Create a new announcement">
    Click **New Announcement**.
  </Step>

  <Step title="Write your message and add media">
    Enter your message text. Attach images, video, or documents as needed.
  </Step>

  <Step title="Choose your audience">
    Select **All staff**, specific locations, departments, or roles. You can combine multiple audience segments.
  </Step>

  <Step title="Set acknowledgment and schedule">
    Enable **Mandatory acknowledgment** if you need an explicit confirmation. Choose whether to send immediately or schedule for a later time. Set a priority level and expiry date if applicable.
  </Step>

  <Step title="Send">
    Click **Send**. Team members receive a push notification and see the announcement in their mobile app.
  </Step>

  <Step title="Monitor read receipts">
    Open the announcement's **Read Receipt** dashboard to see live acknowledgment status by person, location, and team.
  </Step>
</Steps>

## Common use cases

* **Policy rollouts** — new procedures or compliance requirements that all staff must acknowledge
* **Safety alerts** — urgent hazard notices requiring immediate acknowledgment before workers start their shift
* **Product launches** — new menu items, promotions, or service changes communicated before they go live
* **Urgent ops updates** — shift changes, location closures, or equipment issues that need fast, confirmed communication

<Warning>
  If you mark an announcement as **Urgent**, it appears as a persistent banner that blocks dismissal until the worker acknowledges it. Reserve this setting for genuinely time-sensitive situations to avoid alert fatigue.
</Warning>