Skip to main content
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.

Find The Right Guide

Not sure where a feature lives? Start here and choose by job: setup, menus, devices, messaging, content, files, or APIs.

Workspace Setup Checklist

A launch sequence for new workspaces, branches, and teams preparing Plato for daily use.

Launch Playbooks

Step-by-step routes for launching Restaurant, POS/KDS, messaging, Bio Link, CMS, Drive, and integrations.

Team Playbooks

Role-based routes for owners, managers, front-of-house, kitchen, customer care, content teams, and developers.

​
Fast Tracks

Restaurant Launch

Menus, products, online ordering, tables, reservations, reports, devices, and daily operations.

POS And Kitchen

Device setup, POS sessions, kitchen display screens, printing, payments, and call center workflows.

Customer Messaging

Inbox replies, templates, campaigns, AI auto-reply, workflows, links, wallets, and messaging reports.

Public Link Pages

Bio Links, QR codes, social icons, menus, campaign links, translation, appearance, and sharing.

Content And Files

CMS tables, entries, schema fields, relations, developer tools, and reusable content.

Shared Assets

Upload, organize, preview, download, reuse, and select files from other Plato apps.

​
What Plato Area Owns What?

  1. Open Configuration and confirm workspace details, language, currency, and tax settings.
  2. Open Roles and prepare access for the team.
  3. Open Members to invite teammates.
  4. Open Member PINs if the team uses POS, KDS, or shared devices.
  5. Open the product your team needs first, such as Restaurant, Connect360, Bio Link, CMS, or Drive.
  6. Use API Keys only when an integration is ready and its permissions are clear.

​
Still Deciding?

Start with 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.