UI workflow
Scenario
Admin Panel
Log in, search and manage a table of user records — edit a role, suspend an account, add a new user, delete one — then log out and confirm the page is protected again.
How this works
- · Requires a real login (standard_user / Password123!) — the Records page is protected by middleware that redirects unauthenticated visits straight back to Login.
- · The session is a stateless, HMAC-signed cookie, not a database row — it survives server restarts but is entirely private to your browser.
- · The records table lives in that same session's cookie storage — edits, suspends, and deletes only ever affect your own copy, resettable any time via the seed/reset endpoints.
What you'll practice
- A real login-gated page — visiting Records while signed out redirects you straight back to Login
- Searching a table of records client-side
- Editing a role and toggling a status via server-rendered forms, not a client-only illusion
- Adding a new record and deleting an existing one
- Logging out and confirming the page is protected again
- 1 Login →
- 2 Records