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

# Start Here

> Start here to understand Plato, choose the right app, and follow the most useful setup and team playbooks.

Plato is a workspace platform for restaurant operations, customer engagement, public pages, content, files, devices, and integrations.

Use this Start tab as the front desk for the docs. Pick a guide, follow a launch route, or jump into the playbook that matches the team member doing the work.

<CardGroup cols={2}>
  <Card title="Find The Right Guide" icon="compass" href="/start/find-the-right-guide">
    Not sure where a feature lives? Start here and choose by job: setup, menus, devices, messaging, content, files, or APIs.
  </Card>

  <Card title="Workspace Setup Checklist" icon="list-checks" href="/start/workspace-setup-checklist">
    A launch sequence for new workspaces, branches, and teams preparing Plato for daily use.
  </Card>

  <Card title="Launch Playbooks" icon="rocket" href="/start/launch-playbooks">
    Step-by-step routes for launching Restaurant, POS/KDS, messaging, Bio Link, CMS, Drive, and integrations.
  </Card>

  <Card title="Team Playbooks" icon="users" href="/start/team-playbooks">
    Role-based routes for owners, managers, front-of-house, kitchen, customer care, content teams, and developers.
  </Card>
</CardGroup>

## Fast Tracks

<CardGroup cols={3}>
  <Card title="Restaurant Launch" icon="utensils" href="/restaurant">
    Menus, products, online ordering, tables, reservations, reports, devices, and daily operations.
  </Card>

  <Card title="POS And Kitchen" icon="tablet-smartphone" href="/kds-pos">
    Device setup, POS sessions, kitchen display screens, printing, payments, and call center workflows.
  </Card>

  <Card title="Customer Messaging" icon="messages-square" href="/connect360">
    Inbox replies, templates, campaigns, AI auto-reply, workflows, links, wallets, and messaging reports.
  </Card>

  <Card title="Public Link Pages" icon="link" href="/bio-link">
    Bio Links, QR codes, social icons, menus, campaign links, translation, appearance, and sharing.
  </Card>

  <Card title="Content And Files" icon="database" href="/cms">
    CMS tables, entries, schema fields, relations, developer tools, and reusable content.
  </Card>

  <Card title="Shared Assets" icon="folder-open" href="/drive">
    Upload, organize, preview, download, reuse, and select files from other Plato apps.
  </Card>
</CardGroup>

## What Plato Area Owns What?

| Area          | Use It For                                                                                     | Start Here                                  |
| ------------- | ---------------------------------------------------------------------------------------------- | ------------------------------------------- |
| Console       | Workspace settings, team access, domains, API keys, notifications, and app entry.              | [Console](/console)                         |
| Restaurant    | Menus, products, orders, tables, reservations, customers, reports, settings, and devices.      | [Restaurant](/restaurant)                   |
| POS And KDS   | Service devices, kitchen screens, sessions, payments, printing, and call center workflows.     | [KDS/POS](/kds-pos)                         |
| Connect360    | Chat inbox, campaigns, templates, AI auto-reply, workflows, short links, wallets, and reports. | [Connect360](/connect360)                   |
| Bio Link      | Public link pages, QR codes, social links, menus, campaigns, translations, and sharing.        | [Bio Link](/bio-link)                       |
| CMS           | Custom content tables, entries, schema fields, relations, and developer helpers.               | [CMS](/cms)                                 |
| Drive         | Shared files, folders, previews, downloads, reusable assets, and file pickers.                 | [Drive](/drive)                             |
| API Reference | API keys, REST endpoints, CMS APIs, Connect360 APIs, menu APIs, forms, and order feeds.        | [API Overview](/api-reference/introduction) |

## Recommended First Run

1. Open [Configuration](/console/configuration) and confirm workspace details, language, currency, and tax settings.
2. Open [Roles](/console/roles-and-permissions) and prepare access for the team.
3. Open [Members](/console/members) to invite teammates.
4. Open [Member PINs](/console/member-pins) if the team uses POS, KDS, or shared devices.
5. Open the product your team needs first, such as [Restaurant](/restaurant), [Connect360](/connect360), [Bio Link](/bio-link), [CMS](/cms), or [Drive](/drive).
6. Use [API Keys](/console/api-keys) only when an integration is ready and its permissions are clear.

## Still Deciding?

Start with [Find The Right Guide](/start/find-the-right-guide). It maps common jobs to the docs that own them, including setup, menus, devices, customer messaging, public pages, content, files, and integrations.