About Services Tools Blog Contact us

Admin Dashboard with Staff Roles

A starting point for staff tools with login, form protection and settings, where each person can be given access to chosen tools only.

  • Web Tools
  • Cross-sector
  • Tool
  • Product
  • Local/private
  • 2026

The problem

Every new staff tool rebuilt login, form tokens, settings and a sidebar, and the copies drifted apart. A single shared login would let every staff member publish and change connections. So there was no safe way to give someone one tool and withhold another.

What it does

A new tool starts from a ready base that already has login, form protection, a settings screen and locked-down sensitive folders. Administrators can open every tool. Staff start with a small set, and an administrator adds extras person by person on a grid of ticks, so nobody needs a shared login.

Outcomes

  • New staff tools start with login and sidebar already built.
  • Staff see only the modules they are granted.
  • An administrator sees a new module without a database migration.
  • A form with a failed token cannot save settings.

Simplified mockup

Interactive preview with sample data. Nothing is sent to a server.

Staff sign-in

North Quay Leisure

Sample administrator is filled in. The password never leaves this page.

Session
Ready when you are

Module grants

People 4
NameRoleState
Amira ColeAdministratorall modules
Tom HaleStaffselected
Priya NairStaffphoto desk
Owen BlakeStaffdisabled
Ticks for Tom Hale

Effective access is the staff role plus these direct grants.

Sidebar this person would see
Dashboard
Directory
Bookings
Tom Hale

Hidden from the sidebar: Settings, Photo studio, Reports

Resolution
Pick a person, then resolve

Organisation settings

Stored values stay unless the token passes
Stored: North Quay Leisure
Stored: North Quay desk
Stored: 8 hours

Token on this submit: expired

Save
Nothing written yet
Durable echo

Two calls in a row. The second must not wipe the first.

Idle

How it works

  1. Copy the base and sign in as an administrator.
  2. Use the login, dashboard, settings and a small connection for other systems that it already has.
  3. Send forms with a hidden security code, and reject any form with a wrong code.
  4. Create a staff user and tick the tools they may open.
  5. Give each person their role plus those ticked extras.
  6. Apply a disabled user or a password reset straight away.

Pipeline

flowchart LR
  A[Sign in] --> B[Role check]
  B --> C[Module grants]
  C --> D[Sidebar]
  E[Settings form] --> F{Valid token?}
  F -->|Yes| G[Save]
  F -->|No| H[Reject]