feat(supervisor): keep operator records separate from accounts #192

New issue

Open

opened 2026-09-30 15:26:00 +00:00 by gabogg · 0 comments

gabogg commented

2026-09-30 15:26:00 +00:00

Owner

Part of #187 — milestone: Focused operator and supervisor door operations.

Intended outcome

Start with a staff directory for the people who perform door operations. This is separate from creating, editing, or disabling login accounts; shift management is outside the first stage unless later triage adds it. The existing authentication users table and #72 command-audit work remain separate until a relationship is chosen.

Triage questions

Which staff members belong in this directory (including contractors or on-duty contacts), and which minimum fields are useful now?
Are records linked to login users, HikCentral personnel IDs, both, or neither? What happens when names or assignments change?
Which workflows need attribution: manual entries, door commands, exclusions, alarm follow-up? Is a historical snapshot of the person's name required?
Who may view or edit these records, and what personal-data retention or visibility limits apply?

Ready-to-spec outcome

A small domain model for the first stage, the chosen relationship to authentication and #72's audit identity, and a read/write scope that does not manage credentials.

Part of #187 — milestone: Focused operator and supervisor door operations. ## Intended outcome Start with a staff directory for the people who perform door operations. This is separate from creating, editing, or disabling login accounts; shift management is outside the first stage unless later triage adds it. The existing authentication `users` table and #72 command-audit work remain separate until a relationship is chosen. ## Triage questions 1. Which staff members belong in this directory (including contractors or on-duty contacts), and which minimum fields are useful now? 2. Are records linked to login users, HikCentral personnel IDs, both, or neither? What happens when names or assignments change? 3. Which workflows need attribution: manual entries, door commands, exclusions, alarm follow-up? Is a historical snapshot of the person's name required? 4. Who may view or edit these records, and what personal-data retention or visibility limits apply? ## Ready-to-spec outcome A small domain model for the first stage, the chosen relationship to authentication and #72's audit identity, and a read/write scope that does not manage credentials.

gabogg added this to the Focused operator and supervisor door operations milestone

2026-09-30 15:26:00 +00:00

gabogg added the

needs-triage

label

2026-09-30 15:26:00 +00:00

gabogg referenced this issue

2026-09-30 15:26:53 +00:00

epic(ui): focus Operator on doors and alarms; introduce Supervisor workspace #187