π Every dashboard in the suite
One list, every page, grouped by what it's for. Open goes to a new tab; β§ copies the full link for a text or an email. The list is baked into this build β a page added to the suite shows up here at the next rebuild.
β Compliance actions
Actions the app needs from staff, tracked in one place. Today: the Student Data Privacy Training β who is current, who is expiring within 30 days, who has expired and who has never completed it. Every completion is good for one year; the automatic renewal email (trainingRenewals) goes out 364 days after each completion and asks the person to retake the training. β Send renewal now queues that same email by hand. Executives only (the five in csuite).
Sign in to load the chart.
Sign in to load the staff panel.
Partner access requests 0 pending
Every submission of partner-join.html lands here. Approve adds the person to the program directory and the sign-in allow-list, then emails them the hub link. Both the school email and the alternate email are allowed in, so the alternate is the fallback if DOE blocks the school account.
Loadingβ¦
οΌ Add a partner by hand
Current partners
Loadingβ¦
Share the sign-up form
Send the link to the school leader or print the QR. Long form of the same link: partner-join.html?p=<program>
Hub links
π₯ CMSI staff oversight β Phase 2
Planned for this lens, on MJ's word about the data source (the CPO dashboard's staff blocks are the likely port):
- CMSI / ONS-YES roster with reports-to chain (Malcolm Penn's team) and per-person call-outs, WFH and time-off state
- Work Tracker roll-up scoped to CMSI
- Open hires and onboarding requests for the department
π° Budgets β Phase 2
Planned: CMSI program budgets from Master_Program_Budget_FY27 (the Budget Command Center pattern on cm-cpo-dashboard.html), spend-to-date from receipts and bill.com exports, and the FY27 forecast lines MJ owns.