Atlas Tenant Onboarding

W0 · Checklist Home

The gated 30-day checklist

MERIDIAN ROOM · ONBOARDING

DAY 08 OF 30

● ON PACE · 3 OF 5 GATES

DAY 0 · PROVISIONEDDAY 30 · GO LIVE

⚑ REQUIRED GATES· must clear all to go live

●

Tenant provisioned

VENUE · TIMEZONE · CURRENCY SET

● DONE

●

Payments connector live

SQUARE · CONNECTED DAY 3

● DONE

●

Operator grants assigned

4 ROLES · SCOPES MAPPED

● DONE

Connect remaining sources

2 STILL ON SEEDED DATA

◐ IN PROGRESS

○

Review & accept data contract

UNLOCKS WHEN CONNECTORS LIVE

△ LOCKED

OPTIONAL · RECOMMENDED BEFORE NIGHT ONE

●

Import floor plan

18 TABLES MAPPED

● DONE

Invite promoters

0 OF ~6 EXPECTED

○ SKIPPED FOR NOW

Set closeout defaults

USING PLATFORM DEFAULTS

○ OPTIONAL

W1 · Provision

Tenant provisioning form

GATE 01 · PROVISION TENANT

Venue name * DISPLAYED ON VENUE-LINK, WALLET PASS, DOOR

Legal entity *

Tenant slug * atlas.app/t/meridian-room

Timezone * DRIVES NIGHT BOUNDARY & CLOSEOUT WINDOW

Currency * STORED AS INTEGER CENTS · 150000 CENTS = A$1,500.00

Default table minimum CENTS · SHOWN AS A$1,500.00

Deposit % of minimum COUNTS TOWARD MINIMUM · REFUNDABLE 6PM DAY-OF

Density profile

⚑ TAKE-RATE NOT SET HERE · VENUE REPORTING ONLY, NEVER MARKETED

NOTES · Rationale

Required fields carry an amber * — the alarm color's lightest weight, attention not blocking.
Money is captured and stored as integer cents. The field takes cents; the live preview renders the formatted figure so the operator can sanity-check 150000 CENTS = A$1,500.00.
Currency selection re-symbols every money preview on the page — one source of truth for the tenant's display format.
Timezone is load-bearing: it defines the night boundary the whole console pivots on. Called out in the hint, not buried.
Take-rate is deliberately absent from provisioning — ⚑ placeholder, venue reporting only. No rate marketing on an operator surface.
Inputs are SURFACE-2; mono for structured values (timezone, currency, cents), sans for free text (venue name).

W2 · Connectors

Connector states — live · stub · expired

GATE 02 · CONNECT SOURCES

SQ

Square · Payments & tabs

● LIVE · WEBHOOKS RECEIVING

SYNCED 2m AGO142 events today

SP

Spotify · Taste graph

● LIVE · CONSENTED

SYNCED 1h AGOconsent on file

SC

SoundCloud · Taste graph

△ STUB · NO KEY SET

AM

Apple Music · Taste graph

△ STUB · NO KEY SET

TM

Ticketmaster · Demand feed

● LIVE · 74 EVENTS SYNCED

VIA A-LIST FEEDra-cron · nightly

EB

Eventbrite · Demand signals

△ STUB · NO KEY SET

IG

Instagram · Marketing reach

△ STUB · SEEDED DATA

ST

Stripe · Deposits & payments

● LIVE · WEBHOOKS RECEIVING

SYNCED 5m AGOholds + refunds

KL

Klaviyo · Lifecycle & campaigns

● LIVE · SENDING

SYNCED 12m AGOflows active

LS

Lightspeed · POS & inventory

△ STUB · SEEDED DATA

TO

Toast · POS & tabs

● LIVE · WEBHOOKS RECEIVING

SYNCED 3m AGO98 events today

7R

SevenRooms · Reservations

● LIVE · SYNCING

SYNCED 4m AGOreservations mapped

RS

Resy · Reservations

△ STUB · SEEDED DATA

TK

Tock · Reservations

△ STUB · SEEDED DATA

GC

Google Calendar · Event feed

◐ AUTH EXPIRED · TOKEN LAPSED

NOTES · Rationale

Border style is the state — read it before any label.
Solid mint border = LIVE. Carries a recency stamp (SYNCED 2m AGO) so the operator trusts the data is fresh, not just connected once.
Dashed border = STUB · SEEDED DATA. The surface works from day zero on demo data; a cyan CONNECT action swaps seed for real. Cyan = the forward, opt-in action.
Amber solid = AUTH EXPIRED. Alarm's tinted-fill weight — the token lapsed, action needed, but never red. RECONNECT is the recovery path.
Seeded stubs mean a tenant is never blocked by an unconnected source — they go live on seed and upgrade in place.
No connector ever shows red — expired auth is amber, the strongest weight used here.
Klaviyo setup = create one flow per Atlas metric. Delivery is server-side events, never a list blast — Atlas fires a metric event per consented guest and your Klaviyo flow sends the message. Create a flow triggered on each metric you want live: Atlas Event Match, Atlas Regulars Lock-In, Atlas Winback, Atlas Crew Rebook, Atlas Loyalty Claim, Atlas Campaign. A metric with no flow simply does nothing — opt-in per message type. Profiles match on email / phone / external_id (the Atlas guest id).

W3 · Grants

Grant model — SEE is given, DO is granted

GATE 03 · ASSIGN GRANTS · ROLE: FLOOR MANAGER

RESOURCE	SEE	DO · hover for scope
Bookingsheld · confirmed · seated · closed	●ALWAYS	bookings:write
Floor & tablesseat · block · move party	●ALWAYS	floor:manage
Payments & tabsre-request · refund deposit	●ALWAYS	payments:write
Door & check-inscan pass · check in guest	●ALWAYS	door:checkin
Closeout & reconcilerun closeout · reconcile tab	●ALWAYS	closeout:run
Grants & tenantassign scopes · edit tenant	●ALWAYS	tenant:admin

3 DO scopes granted · SEE is universal

W3b · CONFIRM GRANT · WORKED EXAMPLE

This grant lets a Floor Manager, on the night: ● SEE every booking, table, tab and door state for the venue — always, no toggle.
● DO seat a party, block a table, confirm or cancel a held booking bookings:write, and check a guest in at the door door:checkin.
⊘ CANNOT refund a deposit, re-request a failed split-pay share payments:write, run closeout closeout:run, or reassign anyone's grants tenant:admin — those toggles are off.

GRANTED SCOPES · bookings:write · floor:manage · door:checkin

NOTES · Rationale

SEE is always-on, always mint. Every operator sees the whole venue — visibility is never rationed. Rationing sight breaks the shared-truth model the console runs on.
DO is what's granted. Each DO toggle maps 1:1 to exactly one scope string — no bundles, no hidden implied permissions.
Scope strings show on hover only (bookings:write). The table stays human-readable; the raw scope is there for the admin who needs it, out of the way for the one who doesn't.
W3b confirms in plain language with a worked example — what this person can and can't do on the night, not an abstract scope list. The ⊘ CANNOT lines matter as much as the grants.
Toggle on = cyan (the enabling action); off = neutral gray. Never red for an off permission.

W4 · Data Contract

The data contract — and the gate to go live

GATE 05 · REVIEW DATA CONTRACT

↓ FLOWS IN

● square · payments
● square · tab events
● spotify · taste (consented)
● ticketmaster · demand feed
● door · check-in scans

▲ FLOWS OUT

● venue-link · booking
● wallet pass · updates
● closeout · reconciliation
● promoter · settled receipts
● outcomes · pillar scores

⊘ NEVER FLOWS

⊘ guest PII to promoters
⊘ raw card data (tokenized only)
⊘ taste data without consent
⊘ cross-tenant guest graph
⊘ take-rate to guest surfaces

PREREQUISITES FOR GO-LIVE

● Tenant provisioned · currency & timezone set

● Payments connector live · webhooks receiving

● Grants assigned to all operators

△ 2 connectors still on seeded data — connect or accept seed

△ Data contract not yet accepted

⚑ GATED · 2 PREREQUISITES OUTSTANDING ACCEPT DATA CONTRACT (DEMO)

NOTES · Rationale

Three lists, one glance. FLOWS IN (mint), FLOWS OUT (electric), and — the one that builds trust — NEVER FLOWS (amber, tinted panel).
NEVER FLOWS is the point of this screen. Stating the boundaries explicitly — no guest PII to promoters, no cross-tenant graph, no take-rate to guests — is what makes the contract worth accepting.
GO LIVE is gated, not hidden. It renders disabled with a ⊘ glyph and an amber gate-note naming exactly what's outstanding. The operator sees the finish line and the two steps left.
Prerequisites use the same status glyphs as W0 — ● cleared, △ outstanding — so the gate reads consistently with the checklist.
Accepting the contract (demo toggle) clears the last prereq and the button un-gates to a live mint GO LIVE — the one moment mint means "commit".