jb/shd.build
1
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases Wiki Activity

Expand ISAC user operations

Browse Source
This commit is contained in:
JB
2026-07-25 02:54:53 -04:00
parent 22b9e4578c
commit 78dc5dcc98
8 changed files with 169 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/DESIGN_SYSTEM.md
+25
View File
@@ -161,6 +161,31 @@ Use the spacing tokens for new components. Prefer `8px`, `12px`, and `20px` gaps
- The administrative system is named ISAC. Separate navigation into explicit
operational domains such as User Operations and Data Management; visibility
must reflect server-provided capabilities.
- User Operations shows every supported authentication method as operational
metadata: local credentials, verified email, passkeys, Discord, and planned
providers. Identity-removal controls require `users.identities`, create audit
records, and preserve at least one remaining sign-in method.
- The Agent Registry prioritizes assigned roles over authentication-method
summaries. Authentication details belong in the individual agent dossier.
- ISAC authentication-method removal is always a two-step interaction contained
within the affected method row. The confirmation state explains the impact and
provides explicit Cancel and orange Confirm actions before submission.
- Agent dossiers consolidate operational controls into full-width tabs for
Roles & Permissions, Authentication, and Moderation. Keep dense controls in
their relevant tab instead of allowing one dashboard column to grow far beyond
adjacent content.
- Avatar removal uses the same in-card, two-step confirmation interaction as
authentication-method removal.
- Role and permission changes require a modal review step that summarizes the
complete selected role and direct-permission sets. Only the modal's orange
Confirm action submits the assignment.
- Access-review summaries are diffs: retained assignments use a neutral `KEEP`
state, additions use green `ADD`, and removals use red `REMOVE` with struck
assignment text. Added and removed items appear together in their respective
role or direct-permission column.
- Login, build/guide, and comment histories are independent support registries.
Each provides context-appropriate filters and namespaced pagination controls
so changing one history page does not reset the others.
- Each module starts with `module-toolbar`, followed by `module-kpis`.
- Editors use `dashboard-editor` and appear before the affected table.
- Data collections use `dashboard-table`, `dashboard-row`, and `table-heading`.