Quick Start: Implementation Team
Standing up a new location, or embedding public widgets on a marketing site.
This is the path for a team bringing LSCApp into a real operator's business — whether that's initial setup or embedding the public-facing pieces into an existing marketing site.
Standing up a new location
Follow Quick Start: Operator end to end — location basics, staff, catalog, Stripe, approval rules, notifications. That page is the canonical setup checklist.
Two things worth flagging specifically for an implementation team:
- Data migration. If the operator is moving off another platform (Nexudus, OfficeRnD, etc.), plan the migration as its own project: customer records, active leases, and historical billing all need careful, verified mapping — never a blind bulk import. See Migrating From Another Platform.
- Compliance setup. If the operator offers registered/virtual office, the CMRA address and PMB numbering must be configured correctly before the first real Form 1583 is submitted — see Registered-Office Compliance Settings.
Embedding the public booking flow
The public flows (/book, /day-pass, /registered-office,
/offices/browse) are built to be dropped into a marketing site via
<iframe> at a fixed size — no separate integration work needed beyond
the embed itself. See
Wix Iframe Embedding
for the exact pattern, and
Public Booking Widgets
for what each widget covers.
Every one of these flows is guest-checkout by design — a visitor never hits a sign-up wall before paying. Don't add one in front of the iframe either; see Guest Checkout Policy.
Rolling out to staff
Staff accounts are invite-only. Plan a short rollout: invite an ADMIN or two first, have them click through Quick Start: Staff themselves, then invite the rest of the front-desk team once the catalog and approval rules are actually correct — changing prices or thresholds after staff are already relying on them is more disruptive than getting it right first.
Handoff checklist
Before calling a rollout done, confirm:
- Every public flow completes as a guest with no account prompt
- Stripe is on the operator's own account (not a shared test account) before real customer payments start
- At least one OWNER-role account is confirmed working, independent of whoever did the setup
- Refund/approval thresholds reflect the operator's actual policy, not the defaults
- Notification templates use the operator's real business name, not placeholder text