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

# Communications Hub

> Use announcements and structured communications to keep residents informed without losing the audit trail

<Frame caption="Keep everyone in the loop with announcements and polls">
  <img src="https://mintcdn.com/managemanagement/xY5E1zWG_1HYuruH/images/hero-light.svg?fit=max&auto=format&n=xY5E1zWG_1HYuruH&q=85&s=ed29f1ed3aac61163cf8587442eef3cf" alt="Communications Hub" className="w-full rounded-lg" width="800" height="400" data-path="images/hero-light.svg" />
</Frame>

## Overview

Communications in Manage.Management has two layers:

* **Announcements** for building-wide updates that residents need to read and revisit
* **Communications** for management-led messaging with templates, batches, inbox views, and audit history

## How the tools differ

<CardGroup cols={2}>
  <Card title="Announcements" icon="megaphone">
    Best for resident-facing updates, reminders, notices, and ongoing building information.
  </Card>

  <Card title="Communications workspace" icon="mail">
    Best for structured communication runs where templates, recipients, previews, and history matter.
  </Card>

  <Card title="Voting and meetings" icon="check-square">
    Use adjacent workflows when the goal is participation, scheduling, or a formal record rather than a simple update.
  </Card>

  <Card title="Documents" icon="folder-open">
    Pair important messages with the documents residents need to understand the context.
  </Card>
</CardGroup>

## What management users can do

<AccordionGroup>
  <Accordion title="Create messages from templates" icon="file-text">
    Start from a template when you need a repeatable communication pattern across one or more buildings.
  </Accordion>

  <Accordion title="Prepare recipient lists and previews" icon="users">
    Build the audience first, then review how the final communication will appear before sending it.
  </Accordion>

  <Accordion title="Track batches, inbox, and audit history" icon="history">
    Use the wider communications surface when the message needs traceability beyond a one-off announcement.
  </Accordion>

  <Accordion title="Keep communications linked to operations" icon="link">
    Finance changes, maintenance work, meetings, and governance updates are easier to trust when the communication points back to the source workflow.
  </Accordion>
</AccordionGroup>

## Good public-facing practice

<CardGroup cols={2}>
  <Card title="Choose the lightest-weight tool that fits" icon="gauge">
    Use an announcement for a straightforward update, and the communications workspace when the job needs more structure.
  </Card>

  <Card title="Write for residents first" icon="home">
    Even when the trigger is an internal workflow, the published message should explain what residents need to know or do.
  </Card>

  <Card title="Link supporting records" icon="paperclip">
    Important updates are stronger when they reference the relevant notice, budget, minute, or issue record.
  </Card>

  <Card title="Keep the trail tidy" icon="archive">
    Reuse templates and shared records so repeated building communications stay understandable over time.
  </Card>
</CardGroup>
