Bringing a New Site Onto Care Concierge: The First 30 Days

When a new organization joins Care Concierge, it doesn't get bolted onto a shared multi-tenant login screen — it gets its own subdomain, wired through the same wildcard DNS pattern that already routes traffic to every existing site. From the first day, staff sign in at an address with their own organization's name on it, not a generic one shared with every other facility on the platform.

Underneath that branded surface, isolation is enforced at the database layer, not just the URL. Every table that holds tenant data carries a tenant identifier, and row-level security policies check it on every query — a staff member at one site cannot see another site's requests, audit logs, or settings, regardless of what URL they happen to type. The subdomain is a convenience for the person visiting; the actual isolation guarantee lives in the database.

Patient-facing access doesn't require an account at all. Each site gets its QR-code-based request flow configured for its own units and rooms, so a patient scans a code and submits a request without a login — while every request, and everyone who acts on it, is written to an immutable audit log from the first interaction.

The 30-day window is mostly configuration, not development: sites and units mapped to the facility's actual floor plan, staff accounts provisioned with the right roles, QR codes generated and posted, and a short verification pass to confirm requests are routing correctly before the site goes live to real patients.