> ## 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. # Workspace Setup Checklist > A practical order for setting up a new Plato workspace before inviting the full team. Use this checklist when a workspace is new, when a branch is about to go live, or when a team wants to confirm the basics before daily operations begin. Confirm workspace details, business settings, language, currency, tax, and order defaults. Create roles, invite members, and set PINs before staff start using shared devices. Test public pages, connected devices, printing, order flow, and integration access before handoff. ## At A Glance | Stage | Goal | Primary Docs | | -------------------- | --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | | 1. Workspace | Confirm business settings that every app depends on. | [Configuration](/console/configuration) | | 2. Access | Give each teammate the right permissions and PIN. | [Roles](/console/roles-and-permissions), [Members](/console/members), [Member PINs](/console/member-pins) | | 3. Apps | Open the apps the team will use first. | [Open An App](/console/open-an-app) | | 4. Public Experience | Test what customers see before sharing links or QR codes. | [Restaurant](/restaurant), [Bio Link](/bio-link), [Connect360](/connect360) | | 5. Devices | Connect tablets, POS, KDS, printers, and display screens. | [Device Types](/kds-pos/getting-started/device-types), [Connect Devices](/kds-pos/getting-started/connect-devices) | | 6. Integrations | Add API access after permissions are clear. | [API Keys](/console/api-keys), [API Overview](/api-reference/introduction) | ## 1. Confirm Workspace Settings Open [Configuration](/console/configuration) and review the basics first. * Business name and contact details. * Address and map location. * Currency, language, time zone, and tax settings. * Order defaults that affect Restaurant, POS, and customer-facing menus. These settings become assumptions across the workspace, so finish them before building public pages or inviting a large team. ## 2. Create Roles Before Inviting Everyone Open [Roles](/console/roles-and-permissions) and create access groups for the team. Good starting roles are usually: * Owner or administrator for full setup access. * Manager for daily operations, reports, menus, and staff actions. * Cashier or front-of-house for POS and order handling. * Kitchen for KDS and preparation workflows. * Marketing or customer care for Bio Link, campaigns, templates, and inbox replies. After roles are ready, use [Members](/console/members) and [Invitations](/console/invitations) to add the team. ## 3. Add Member PINs For Device Work If the team will use POS, KDS, or other staff-facing devices, set PINs from [Member PINs](/console/member-pins). PINs make shared devices easier to use while still keeping actions tied to the right staff member. ## 4. Open The Apps You Need From the Console dashboard, use [Open An App](/console/open-an-app) to enter each active Plato app. For most teams, start with: * [Restaurant](/restaurant) for menus, orders, tables, reports, and restaurant settings. * [Drive](/drive) for shared images, PDFs, videos, and reusable files. * [Bio Link](/bio-link) for a public link page and QR-friendly customer entry point. * [Connect360](/connect360) for chat, templates, campaigns, and customer messaging. * [CMS](/cms) when custom content tables are needed. ## 5. Prepare The Public Customer Experience Before sharing links or QR codes, check every page a customer can see. * In Restaurant, test the public menu, product details, checkout fields, order types, charges, and availability. * In Bio Link, check profile details, buttons, social icons, translations, and QR code downloads. * In Connect360, test templates, channels, wallet balance, and campaign links. * In Drive, confirm public assets preview correctly where they are used. ## 6. Connect Devices And Run A Service Test For restaurant operations, create and connect devices before launch. * Use [Device Types](/kds-pos/getting-started/device-types) to decide which devices are needed. * Use [Create Devices](/kds-pos/getting-started/create-devices) to add them in Plato. * Use [Connect Devices](/kds-pos/getting-started/connect-devices) to link tablets, printers, KDS, or display screens. * Start a POS session, place a test order, send it to the kitchen, print what should print, and close the order. ## 7. Add Integration Access Last Create API keys only after roles and permissions are clear. Use [API Keys](/console/api-keys) for key creation, then continue with [API Overview](/api-reference/introduction), [Authentication](/api-reference/authentication), and the API family your integration needs. Keep integration roles narrow. A reporting tool, a CMS sync, and a restaurant order feed usually do not need the same permissions. ## Ready To Review Before the workspace is handed to the full team, confirm: * Workspace settings match the business. * Roles and member access are correct. * PINs are set for staff who use shared devices. * Public menus, Bio Links, forms, and campaign links were tested. * Devices are connected and a test order completed. * API keys are limited to the integration they belong to.