Sign in (US)
Each region has its own user pool in its own data pod. Roles decide what you can see and do; every sign-in is recorded in the audit log.
Staff
One application’s journey; your seat handles one part of it, and sees only what that part needs.
1
ApplyCAF, both paths2
LocalityConflict gate, LAF3
ATL AssessmentResearch and recommendation4
AdministrationVerification and TARP5
Core TeamReadiness review6
BoardAgenda and decision7
ArchiveCAF + TARP PDFs, reporting- An LCC sees only their locality; an ATL sees their assigned area; the Global Lead sees aggregates only.
- A conflict-of-interest declaration gates every case before it opens.
- A safeguarding concern can be raised from any screen and bypasses local review entirely.
Demo seats in this region (fictional people)
| Name | Role |
|---|---|
| Cole Barrett | Locality Care Contact (LCC) |
| Remy Ortega | Administration |
| Harlan Reyes | ATL (Area Team Lead) |
| Marta Villanueva | Trustee |
| Sky Tanaka | Policy Manager |
| Noor Haddad | Safeguarding Lead |
Demo credentials are in the demo pack, not on this page.
Design note. Real per-region auth pools: the password check runs against this region’s own identity store, and reads carry the signed-in user’s row-level security identity.