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

# Document Management

> Store, organise, preview, and share building records in a searchable repository

<Frame caption="All your building documents in one secure location">
  <img src="https://mintcdn.com/managemanagement/xY5E1zWG_1HYuruH/images/hero-light.svg?fit=max&auto=format&n=xY5E1zWG_1HYuruH&q=85&s=ed29f1ed3aac61163cf8587442eef3cf" alt="Document Management" className="w-full rounded-lg" width="800" height="400" data-path="images/hero-light.svg" />
</Frame>

## Overview

The **Documents** workspace is the shared repository for the records that support building operations. It is designed to keep legal, financial, insurance, maintenance, and admin files easy to find without scattering them across inboxes and drives.

## Core document categories

| Category            | Typical examples                                             |
| ------------------- | ------------------------------------------------------------ |
| **Legal Documents** | Leases, notices, legal correspondence, statutory records     |
| **Financial**       | Accounts, budgets, service-charge records, financial reports |
| **Insurance**       | Policies, certificates, claims, renewals                     |
| **Maintenance**     | Contracts, inspection reports, repair documentation          |
| **Admin**           | Meeting minutes, correspondence, governance records          |

You can also create custom categories when the default structure is not enough for your building or portfolio.

## What users can do in the current product

<CardGroup cols={2}>
  <Card title="Upload and organise" icon="file-up">
    Add new files, place them in the right category, and apply tags or metadata that make later search easier.
  </Card>

  <Card title="Preview and download" icon="eye">
    Open a document from the repository instead of asking users to download everything first.
  </Card>

  <Card title="Search and filter" icon="search">
    Narrow the list by search term, category, tags, or custom category so important records stay easy to find.
  </Card>

  <Card title="Rename, retag, and tidy up" icon="tags">
    Keep the repository readable as the building grows instead of treating upload as a one-way archive.
  </Card>
</CardGroup>

## Analyse a document with AI

Any document in the repository can be run through the **Document Analyser**. Click **Analyse** on a document to get:

* A **structured summary** — key parties, dates, financial terms, property details, and important clauses.
* An **Ask Questions** chat — ask the document things like *"Who is responsible for window repairs?"* and get answers grounded in its contents.

It works best on leases, deeds, licences, contracts, insurance policies, and meeting minutes. See the [Document Analyser guide](/features/document-analyser) for a full walkthrough.

## Why documents matter across the product

<AccordionGroup>
  <Accordion title="Meetings and voting" icon="calendar">
    Agenda packs, notices, minutes, and supporting files are easier to trust when they live with the building record.
  </Accordion>

  <Accordion title="Finance" icon="coins">
    Budgets, accounts, invoices, and Section 20 support files are more useful when the document repository stays up to date.
  </Accordion>

  <Accordion title="Issues and maintenance" icon="triangle-exclamation">
    Inspection reports, warranties, certificates, and supplier paperwork all become easier to reuse when stored centrally.
  </Accordion>
</AccordionGroup>

## Public-facing guidance

<CardGroup cols={2}>
  <Card title="Create a filing habit early" icon="tag">
    The repository is most valuable when teams upload core records as they work, not months later.
  </Card>

  <Card title="Use meaningful categories and tags" icon="tags">
    Search only works well when uploads are organised consistently.
  </Card>

  <Card title="Think about resident readability" icon="home">
    A resident looking for insurance or accounts should not need internal knowledge to find them.
  </Card>

  <Card title="Treat documents as shared context" icon="link">
    Link related meetings, finance workflows, and issue records back to the relevant files where possible.
  </Card>
</CardGroup>
