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

# Launch Playbooks

> Practical Plato setup routes for the most common launch scenarios.

Use these playbooks when the team knows the outcome it wants and needs a clean order of operations.

<CardGroup cols={2}>
  <Card title="Restaurant Online Ordering" icon="utensils" href="/restaurant/menu-management/menus/create-menu">
    Build the menu, add products, configure ordering, test checkout, and share the public menu.
  </Card>

  <Card title="POS And Kitchen Service" icon="tablet-smartphone" href="/kds-pos/getting-started/device-types">
    Create devices, connect tablets and printers, start a session, send orders to KDS, and close a test order.
  </Card>

  <Card title="Customer Messaging" icon="messages-square" href="/connect360/chat-inbox">
    Connect channels, prepare templates, work the inbox, enable AI where needed, and review campaign results.
  </Card>

  <Card title="Public Links And QR" icon="qr-code" href="/bio-link/create-and-manage">
    Create a Bio Link, add customer actions, tune appearance, check translations, and download the QR code.
  </Card>

  <Card title="Content And Assets" icon="folder-open" href="/drive">
    Upload files, create CMS tables, add entries, and reuse assets across menus, campaigns, links, and websites.
  </Card>

  <Card title="Developer Integration" icon="braces" href="/api-reference/introduction">
    Create a scoped role, issue an API key, choose a REST endpoint, and test a small request before production use.
  </Card>
</CardGroup>

## Restaurant Online Ordering

Best when the team wants customers to browse a menu and place orders online.

1. Confirm workspace settings in [Configuration](/console/configuration).
2. Create or review categories from [Categories](/restaurant/menu-management/categories).
3. Add products from [Products](/restaurant/menu-management/products).
4. Create the menu from [Create A Menu](/restaurant/menu-management/menus/create-menu).
5. Add products to the menu from [Add Products To The Menu](/restaurant/menu-management/builder/add-products).
6. Configure order types, customer fields, and operating hours from [Ordering](/restaurant/menu-management/menu-settings/ordering).
7. Preview the public menu from [Check Public Menu](/restaurant/menu-management/public-menu/check-public-menu).

## POS And Kitchen Service

Best when staff need tablets, printers, kitchen displays, and payment workflows ready for service.

1. Choose devices from [Device Types](/kds-pos/getting-started/device-types).
2. Create device records from [Create Devices](/kds-pos/getting-started/create-devices).
3. Connect devices from [Connect Devices](/kds-pos/getting-started/connect-devices).
4. Set device behavior from [Devices And POS](/restaurant/settings/devices-and-pos).
5. Start service from [Start Session](/kds-pos/pos/start-session).
6. Create a test order from [Create Order](/kds-pos/pos/create-order).
7. Test payment, printing, KDS routing, and order closing before the first shift.

## Customer Messaging

Best when the team needs shared inbox replies, campaigns, templates, automation, and customer records.

1. Open [Connect360](/connect360/open-and-navigate).
2. Connect messaging channels from [Channels](/connect360/channels).
3. Prepare reusable messages from [Create A Template](/connect360/templates/create-template).
4. Work daily replies from [Chat Inbox](/connect360/chat-inbox).
5. Add customers or segments from [Customers](/connect360/customers).
6. Create campaigns from [Create A Campaign](/connect360/campaigns/create-campaign).
7. Review results from [Reports](/connect360/reports).

## Public Links And QR

Best when customers need one simple page for menus, WhatsApp, maps, booking, campaigns, documents, or forms.

1. Create the page from [Create And Manage](/bio-link/create-and-manage).
2. Add actions from [Builder](/bio-link/builder).
3. Tune profile, colors, fonts, and block style from [Appearance](/bio-link/appearance).
4. Add social icons and URL settings from [Settings](/bio-link/settings).
5. Add translations from [Translations](/bio-link/translations) when needed.
6. Test what visitors see from [Public Page](/bio-link/public-page).
7. Share the page or download the QR code from [Share And QR](/bio-link/share-and-qr).

## Content And Assets

Best when teams need reusable files, structured records, custom content, or developer-readable data.

1. Upload shared files from [Upload Files](/drive/upload-files).
2. Organize assets from [Files And Folders](/drive/files-and-folders).
3. Create content tables from [Create A Database](/cms/databases/create-database).
4. Add fields from [Add Fields](/cms/schema/add-fields).
5. Add records from [Create And Edit Entries](/cms/entries/create-and-edit).
6. Reuse files from [Use Drive From Other Apps](/drive/use-drive-picker).
7. Open [Developer Tools](/cms/developer/tools) if another app or website needs the content.

## Developer Integration

Best when another system needs stable access to Plato data.

1. Create a narrow integration role from [Roles](/console/roles-and-permissions).
2. Create the key from [API Keys](/console/api-keys).
3. Read [Authentication](/api-reference/authentication).
4. Choose a REST API for [CMS](/api-reference/cms/overview), [Restaurant Menu Products](/api-reference/restaurant/menu-products), [Restaurant Orders Feed](/api-reference/restaurant/orders-feed), [Aggregator Orders](/api-reference/aggregators/overview), or [Forms](/api-reference/forms/submit-response).
5. Review [Errors And Limits](/api-reference/errors-and-limits).
6. Test with one small request before syncing production data.