The activation queue (platform)

/platform → Activation queue lists active, non-sandbox organisations that have never published a roster — the ones likely stuck in onboarding. For each one it shows the last completed setup step, a suggested next action, and recency signals (stalled days, last roster change, created date).

The setup-step ladder is derived from current state (the platform keeps no step history):

• 0 — Org created: account exists, onboarding wizard not finished.
• 1 — Onboarding complete: wizard done, no locations or positions yet.
• 2 — Schedule grid ready: locations/positions exist, no shifts yet.
• 3 — Roster drafted: draft shifts exist, nothing published.

An organisation leaves the queue automatically the moment it publishes any roster — a published shift or a deployment publication row.

Practices

• The queue is read-only by design. It cannot send email, SMS, or notifications — outreach requires a human, acting outside the console. The "suggested next action" panel is draft reference copy for that human.
• Rows are sorted oldest-created first by default, which matches triage priority: an org that has sat at step 0 for weeks is a different problem from one that drafted a roster yesterday.
• Use the step summary cards as a rough funnel: many orgs clustered at one step usually points to a product or help-doc problem there, not N separate customer problems.
• Progress toward first-roster publication is simply the queue shrinking: every publish removes an org from this list. Count the queue each week (plus the per-step histogram) to see activation improve.