Overview
A users template aligns directory, profile, and invitation workflows for faster onboarding.
The pattern supports safe editing and auditability for identity operations.
Adapt a directory-to-user workflow
Search the directory, invite a member, move between profile, access, and support context, change roles, and manage suspension with traceable feedback.
Users
Move from directory discovery to profile, access, and support outcomes safely.
Maya Chen
maya@omverse.dev · Platform
- Team
- Platform
- Authentication
- SSO · MFA Verified
- Active sessions
- 3
- Last activity
- 18 minutes ago
Anatomy
Use each piece in this order to keep interpretation and automation consistent.
- 1Directory table
Searchable list with essential identifiers.
- 2Profile summary
Quick snapshot of selected user context.
- 3Role actions
Assign, revoke, and escalate with policy checks.
- 4Invite flow
Onboard via email and role mapping.
- 5Compliance panel
MFA, reset, and ownership metadata.
The ordering here is not visual-only; it reflects interaction priority and expected user cognition. Keep this order unless policy demands a specific domain exception.
When to use
Use this pattern when the user needs guided consistency, state, and reuse at scale.
Recommended
- Administration consoles
Use for internal user management tasks.
- Support tooling
Use when support teams manage user outcomes.
- Tenant setup
Use to onboard teams with roles and access.
When not to use
Avoid forcing this pattern where simpler, direct interactions are sufficient.
Avoid
- Customer self-service account
Use profile setting screens for user-centric tasks.
- Single sign-on only
Use dedicated SSO and directory administration tooling.
- Simple lists
Avoid for read-only user browsing.
Variants
A small number of variants helps teams choose correctly without adding complexity.
Directory-first
Primary focus on users and search.
Governance-first
Role and policy emphasis.
Support-first
Communication and status emphasis for requests.
States
States communicate readiness, risk, and expected user behavior.
| State | Trigger | Visual response | Interaction |
|---|---|---|---|
| Invited | User pending activation | Pending status and activation action | Resend invites and reminders. |
| Active | Verification complete | Active badge and permissions visible | Enable role and reset actions. |
| Suspended | Manual disablement | Lock indicator and restricted actions | Enable with approvals. |
Behavior
Behavior should remain predictable across devices, permissions, and async edges.
Search-heavy
Support direct query and advanced filters.
Scoped actions
Action surface constrained by policy context.
Invite lifecycle
Invite and reset operations are recoverable and auditable.
Accessibility
Keep interaction clarity high and ensure assistive technologies get the same meaning.
| Key | Action |
|---|---|
| I | Open user invite panel. |
| S | Set focus on search field. |
| Ctrl/CmdR | Refresh users from directory provider. |
- Clearly label role changes as advisory or final.
- Keep list headers discoverable and sortable.
- Avoid showing only icons for profile state.
Content guidelines
Consistency is achieved by language standards, not by design only.
Names
Use full name and handle in profile headers.
Sasha Tan (sasha.t)
Invite messaging
State expected next steps.
Invite sent. User can activate via email.
Policy text
Use plain terms for role effects.
Can approve expenses up to $10,000
Examples
Reference implementation style, payloads, and practical behavior.
Production use
- Surface compliance state (MFA, SSO state) beside user role.
- Use bulk role actions for large org changes.
- Require confirmations before suspension and privilege removals.
Props / API
Use these API entries as a baseline contract and validate them against your domain layer.
These names are implementation-oriented and should map to your local contracts.
Props