Blaze Client Workspace Provisioning (Onboarding)

Blaze Client Workspace Provisioning (Onboarding)

1. 01

   Create the client workspace in Blaze and assign role-based permissions before any builder work begins

   Keep agency builders on an admin role and client staff on a restricted role so audit logging captures who changed which app. Enable SSO/2FA at the workspace level on day one, not after the first patient record lands.

2. 02

   Confirm the plan tier against the client's published-app and end-user counts

   Production at $750/month covers 1 published app and up to 100 end users with no per-seat fees. Growth at $2500/month raises that to 5 published apps and 1,000 users plus public forms and guided implementation. Size the tier to the client's real headcount before signing, because a clinic that grows past 100 users forces a mid-engagement upgrade conversation.

3. 03

   Request the BAA through Blaze before the client's first PHI field is created

   Blaze signs a BAA in days on the Production tier and runs on HITRUST e1 and SOC 2 Type II infrastructure. File the signed BAA in the client's compliance folder and note the date in the delivery tracker; healthcare procurement teams will ask for it during their own review.

4. 04

   Build the first workflow in a sandbox environment using the drag-and-drop builder and Blaze Tables

   Model patient records and form submissions as relational tables, then wire conditional logic triggers for reminders and staff notifications. Multi-environment deployment lets you test in sandbox and promote to production without exposing live patient data to unfinished logic.

5. 05

   Connect the client's EHR through FHIR or REST APIs and validate against a test record set

   Native integrations include Athenahealth and FHIR-compliant systems. Run a read and a write against a non-production record before go-live, and document which fields map where so the client's IT contact can sign off.

6. 06

   Publish the app, hand over credentials, and schedule the staff training session

   Walk client staff through the published app and the admin view they will actually use. Record the session and store it with the app architecture documentation so the retainer does not absorb repeat onboarding questions.

7. 07

   Log the workspace in the agency's Blaze portfolio register with tier, BAA date, and renewal month

   Track every client workspace in one place. Enterprise white-labeling and custom branding require direct negotiation with Blaze sales, so flag any client who asks for branded deployment early rather than promising it inside a fixed-fee build.