> ## 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.

# Dashboard

> A role-based control centre for building operations, resident visibility, and portfolio work

<Frame caption="See everything at a glance">
  <img src="https://mintcdn.com/managemanagement/xY5E1zWG_1HYuruH/images/hero-light.svg?fit=max&auto=format&n=xY5E1zWG_1HYuruH&q=85&s=ed29f1ed3aac61163cf8587442eef3cf" alt="Dashboard Overview" className="w-full rounded-lg" width="800" height="400" data-path="images/hero-light.svg" />
</Frame>

## Overview

The dashboard is not a single universal screen. Manage.Management changes the landing experience based on who you are and what you manage, so the first actions for a director, resident, and management-company user are different.

## Dashboard types in the current product

<CardGroup cols={2}>
  <Card title="Director dashboard" icon="building-2">
    Focuses on building setup, issues, finances, documents, meetings, voting, and announcements.
  </Card>

  <Card title="Resident dashboard" icon="home">
    Highlights the information residents usually need first: updates, issues, money, documents, meetings, and votes.
  </Card>

  <Card title="Management-company dashboard" icon="briefcase">
    Adds portfolio-level visibility, building switching, staffing context, and operational shortcuts.
  </Card>

  <Card title="RTM journey views" icon="scale">
    RTM-related users can also see RTM progress and, where available, access formation-specific workflows.
  </Card>
</CardGroup>

## What you can usually expect to find

<AccordionGroup>
  <Accordion title="Building or portfolio summary" icon="building">
    A top-level summary gives context for the currently selected building, or for a wider portfolio if you are a management-company user.
  </Accordion>

  <Accordion title="Action-oriented shortcuts" icon="bolt">
    Common next steps surface directly from the dashboard, such as building setup, issue reporting, document access, or operational review.
  </Accordion>

  <Accordion title="Open work and activity" icon="clock-rotate-left">
    Dashboards usually surface the current work queue: outstanding issues, recent operational activity, meeting requests, or unresolved resident actions.
  </Accordion>

  <Accordion title="Money, meetings, and communications context" icon="calendar-days">
    Depending on your role, you may see financial summaries, upcoming meetings, active votes, or recent building announcements.
  </Accordion>
</AccordionGroup>

## Role-based differences that matter

| Role                            | Typical dashboard emphasis                                                                      |
| ------------------------------- | ----------------------------------------------------------------------------------------------- |
| **Directors**                   | Building setup, governance, issue oversight, finances, documents, and operational quick actions |
| **Leaseholders / shareholders** | Personal property view, current building updates, money, meetings, votes, and issues            |
| **Management companies**        | Building selector, portfolio context, team-led actions, and cross-building operations           |

## Best use of the dashboard

<CardGroup cols={2}>
  <Card title="Use it as a launchpad" icon="rocket">
    The dashboard works best when it sends you into the right operational area instead of trying to replace them.
  </Card>

  <Card title="Check the selected building" icon="map-pin">
    This is especially important for management-company users before acting on issues, finances, or communications.
  </Card>

  <Card title="Move from alerts to records" icon="folder-open">
    If something matters, follow it through to the relevant issue, document, meeting, or finance entry.
  </Card>

  <Card title="Expect your view to change" icon="users">
    Different users in the same organisation will see different cards and shortcuts based on their permissions.
  </Card>
</CardGroup>

<Tip>
  If you are documenting an operational process internally, link people to the destination workspace (`Issues`, `Finances`, `Documents`, `Meetings`) rather than telling them to stop at the dashboard.
</Tip>