Portals
One sign-in, three front doors
The solicitation calls for multiple password-protected portals behind single sign-on. This page sketches that architecture: one identity, role-based access, no second passwords.
Demonstration pattern The sign-in below is a non-functional mock. In production it federates with the State's identity provider over SAML 2.0 or OpenID Connect.
Sign in
Students, families, and staff use the same button. What you see after sign-in depends on who you are, not which link you clicked.
Why single sign-on
- No separate website password to forget or phish
- Access ends automatically when a student graduates or staff depart
- One audit trail across every portal
Who sees what
| Capability | Student | Family | Faculty & staff |
|---|---|---|---|
| Handbook, forms, and announcements | Yes | Yes | Yes |
| Course materials and schedules | Yes | View | Yes |
| Residential fee payment | No | Yes | No |
| Content editing in the CMS | No | No | By role |
| Approval of pending content | No | No | Approvers only |
Editing rights flow into the same workflow shown in the staff CMS demo: an editor in the Communications office drafts, an approver publishes, and the audit log keeps the receipts.