current launch blocker
Do next: Use a RaveFocus-owned Graph app registration or tenant-owned PnP ClientId, then retry only task requests.
not ready for worker launch
This is the front door for the remaining manual Microsoft setup. Follow the cards in order; do not switch forms live, apply protected auth, or invite workers until verification passes.
Do next: Use a RaveFocus-owned Graph app registration or tenant-owned PnP ClientId, then retry only task requests.
not ready for worker launch
Refresh stale Microsoft/Azure sign-in before SharePoint admin consent, List creation, Planner Premium ID capture, Power Automate setup, or the final launch retry.
not ready for worker launch
Run one command to retest Planner visibility, SharePoint Graph access, worker Lists, and whether website forms can leave draft-safe mode.
run before each launch attempt
Bind workers.ravefocus.com and creators.ravefocus.com to the Azure worker quest hub, update GoDaddy DNS, verify DNS proof, and keep SharePoint as the work/data hub.
domain finalization applied and verified
Decide whether to keep the Azure app as the running portal with SharePoint as the data/work hub, or create true worker and creator SharePoint sites before launch.
site-area decision ready after SharePoint/auth setup review
Dry-run-first owner/admin packet for creating 2 true SharePoint sites only after DNS, Lists/forms, auth, and owner approval are ready.
dry-run ready - true SharePoint sites still require owner/admin apply decision
Approve admin consent, retry task requests first, then create 32 Lists, including 15 worker-facing Lists, from CSV templates.
manual SharePoint setup required
Confirm the current Microsoft account can see the intended Planner plans before replacing or reconciling website task IDs.
current account sees 0 Planner plans
Create 7 Premium plans, apply the 15 field pool, then use the owner action sheet to capture actual Premium IDs and URLs.
manual premium ID capture pending
Capture actual IDs/URLs for 32 Lists, 7 Premium plans, 9 flows, and access roles.
capture actual Microsoft IDs after manual setup
Run the 6 handoff steps after Lists and Premium pieces exist.
not ready for worker launch
Build 9 flows after SharePoint Lists exist.
manual flow ID capture pending
Apply Microsoft auth only after 4 roles are assigned, 7 owner actions are checked, and protected-route testing is ready.
prepared; not enforced
Run the final launch preflight before forms-live mode, protected auth, or worker invitations.
not ready for worker launch