cascades: ingest staff CSV + AD/M365 user rollout plan
Meredith/John returned the staff-editor questionnaire (70 people, 11 departments). CSV ingested to reports/; p2-staff-candidates.md updated with real persona breakdown. Wrote full AD/M365 user rollout plan (8 personas, license mapping, OU/group layout, CA policies, 4-wave sequence, 8 open decisions). Drafted follow-up email for remaining open items — Howard will edit and send. Britney Thompson and Polett Pinazavala confirmed still employed (were absent from the CSV return). Christine Nyanzunda confirmed as one person with two roles. Usernames locked for new accounts: Alma.Montt, Kyla.QuickTiffany. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,41 @@
|
||||
# Follow-up email — four open items from the staff list
|
||||
|
||||
**To:** Meredith Kuhn, John Trozzi (cc: Ashley Jensen)
|
||||
**From:** Howard Enos — Computer Guru
|
||||
**Date:** 2026-04-22
|
||||
**Subject:** Got the staff list — thank you. Four small follow-ups before I set up accounts.
|
||||
|
||||
---
|
||||
|
||||
Meredith / John,
|
||||
|
||||
Thank you for sending back the staff list — that's exactly what I needed and it's going straight into the account setup plan. Before I start creating M365 accounts and access policies, I want to confirm a few small things so I don't make the wrong call on any of them:
|
||||
|
||||
1. **Kyla Quick Tiffany** — is her last name three separate words (Quick Tiffany), hyphenated (Quick-Tiffany), or is one of those actually a middle name? I want the account to match whatever her ID / payroll uses.
|
||||
|
||||
2. **Ederick Yuzon** — just confirming the spelling of the first name. "Ederick" vs "Edrick" vs something else?
|
||||
|
||||
3. **Christine Nyanzunda (Memory Care Admin Assistant)** — I originally had her on the caregiver shift-staff list as well. The staff list you sent back only has her once, under Memory Care admin. Can you confirm she's one person with one account, not two? (Account-wise it matters because the admin and caregiver tiers get different licenses and phone access.)
|
||||
|
||||
4. **Alma R Montt (Life Enrichment)** — the title field on her row came back blank. What's her actual title / role so I can put it on the account?
|
||||
|
||||
5. **Britney Thompson** — she's in Active Directory today as a Memory Care Nurse with a real account, but she's not on the list you sent back. Did she leave, is she part-time / on leave, or should she still be there? If she's gone I'll disable the account (and recover the license).
|
||||
|
||||
6. **Polett Pinazavala** — I had her on my caregiver roster (AM, Memory Care, MedTech) from earlier notes, and she's not on the returned list either. Same question — did she leave?
|
||||
|
||||
One related decision I still need from you when you have a minute:
|
||||
|
||||
> Do you want **all staff restricted to signing in only from the building**, or just certain roles (e.g. front desk / kitchen / clinical)?
|
||||
|
||||
The staff list confirms who's on D+P vs. D-only vs. P-only, but "restrict everyone to the building" vs. "only restrict some" changes the license count (it roughly doubles the P2-equivalent licenses we'd buy) and the Conditional Access policy design. Either answer is fine — I just need the call.
|
||||
|
||||
No rush. Whichever of you can reply fastest on the five spellings/titles will unblock me; the building-vs-selective question can wait another day or two if you want to think about it.
|
||||
|
||||
Thank you —
|
||||
|
||||
Howard
|
||||
|
||||
---
|
||||
|
||||
*Draft — prepared 2026-04-22 after processing the staff-editor CSV return.*
|
||||
*Related: `reports/cascades-staff-2026-04-22.csv`, `docs/cloud/p2-staff-candidates.md`.*
|
||||
Reference in New Issue
Block a user