Skip to main content
The rollout keeps the original 14 enabled Locations and adds new customer Locations created on or after October 5, 2026 at 00:00 America/Denver (06:00 UTC). The original group includes one internal pilot; customer communication approvals must exclude that pilot.

​
How enrollment works

Automatic enrollment is off until ONBOARDING_NEW_LOCATION_ENROLLMENT_ENABLED=true is configured. Installation, reauthorization and completed provisioning then check the Location’s creation date directly with the CRM. A new app installation on an older Location does not qualify it for the rollout. The Location must belong to the Operations agency and have a SaaS subscription reference for that same Location and agency. Operations, known internal admin Locations and agency sub-accounts are excluded. Missing or conflicting evidence leaves the feature unchanged. A subscription reference alone is not proof that payment was collected. The app enables Onboarding & Setup in that Location’s Labs settings and records an audit entry. Existing explicit on/off choices are preserved, including manual opt-outs. An agency-level off setting also stops new enrollment. Do not enable the feature for the whole agency to implement this rollout: that would include older Locations.

​
What happens afterward

If automatic account linking is separately enabled, the guarded linker checks the customer subscription and existing Onboarding opportunity. See Automatic account links. Enrollment does not enable customer messages, approve KYC or compliance, mark payment verified or move opportunities. A separately reviewed engine enrollment policy can admit verified new customers after linking; it remains off until configured. Customer messages retain their own permissions and activation. Missing provider data is retried after one, five and fifteen minutes. Exhausted attempts appear in server diagnostics without provider bodies or credentials. After correcting the connection or subscription, technical staff can retry enrollment by Location ID; no provisioning job or reauthorization is required. Reauthorization also retries. Enrollment and account linking have independent retry windows. Account links already marked for review remain a staff task.

​
Pause or undo

Turn off the enrollment configuration to stop future automatic enrollment. Existing Labs settings remain intact. Turn Onboarding & Setup off for an individual Location in Labs to opt it out; retries and reinstalls preserve that choice. To bring an opted-out customer back, explicitly enable the feature in Labs. Before activation, review any Locations created between the cutoff and deployment. They may have already passed the install hook. Technical staff use onboardingEnrollment:afterProvisioning with the verified Location ID, including for installed customers who have no provisioning job. The action rechecks creation date, agency, subscription and opt-outs; it cannot bulk-enable older accounts.