Appearance
User Behavior Manifest v1
This file contains user-facing users-module behavior extracted from the codebase and filtered to high-confidence evidence only.
- Scope: user_users
- Generated At: 2026-05-14T14:21:48.708Z
- Files Scanned: userFiles=1, relatedFrontendFiles=6, apiFiles=15, backendFiles=43
Pages
- Users (/users) [confidence: high] [source: users]
Controls
- Create User [button] in users_page [confidence: high] [source: users]
- Save Settings [button] in escalation_settings [confidence: high] [source: users]
- Login as User [button] in users_table [confidence: high] [source: users]
- Edit [button] in users_table [confidence: high] [source: users]
- Delete [button] in users_table [confidence: high] [source: users]
- Create or Update User [button] in user_modal [confidence: high] [source: users]
- Protected owner warning [message] in user_modal [confidence: high] [source: users]
Flows
- Create user: Open the Users page. -> Click Create User. -> Enter the user details. -> Configure notifications and access scope. -> Save the user. [confidence: high]
- Edit user: Open the Users page. -> Choose a user. -> Open the edit form. -> Update the user details. -> Save the user. [confidence: high]
- Delete user: Open the Users page. -> Choose a user. -> Delete the user. -> Confirm the deletion. [confidence: high]
- Login as user: Open the Users page. -> Choose an eligible user. -> Click Login as User. -> Switch into the selected user session. [confidence: high]
- Save alarm escalation settings: Open the Users page. -> Review the alarm escalation settings card. -> Update escalation timing or stop conditions. -> Save the settings. [confidence: high]
Constraints
- Login as User is only available for eligible active non-owner users and only when the current user has the required owner permissions. [permission] [confidence: high] [source: users]
- Protected owner accounts have restricted editing and cannot be deleted. [protection] [confidence: high] [source: users]
- When messaging alerts are enabled, a valid phone number is required. [validation] [confidence: high] [source: users]
- At least one alarm severity must be selected for notifications. [validation] [confidence: high] [source: users]
- Assigned assets and assigned devices depend on whether global asset or device access is enabled. [dependency] [confidence: high] [source: users]
- Alarm escalation behavior can be configured with timing thresholds and stop conditions. [status_behavior] [confidence: high] [source: users]
- The user form can show a warning when the selected account is a protected owner account. [warning] [confidence: high] [source: users]
Tables
- users-table: User [confidence: high] [source: users]
Forms
- user-upsert-form: Name [confidence: high] [source: users]
- alarm-escalation-settings-form: L1 → L2 (minutes), L2 → L3 (minutes), Stop on Ack, Stop on Clear | sections: Alarm Escalation Settings [confidence: high] [source: users]
Unknowns
- None verified
