Admin overview
Manage users, roles, and governance settings.
Last updated:
Use Settings → Admin for team access, governance controls, and support request triage.
Users
Manage account access for team members.
Admin user detail includes a collapsed Record change history card for record-level audit events on the user record.
On narrower layouts, the Name column becomes the primary summary cell. When the standalone Status column is hidden, the user status badge folds into Name.
The Last sign-in column is populated from successful password and magic-link sign-ins. Invited users or users who have not signed in yet show no last sign-in timestamp.
Password sign-in enforces a 12-character minimum and requires at least one special character. New account passwords, admin-created temporary passwords, and password resets must satisfy the same policy.
Passwords expire after 365 days. Expired passwords must be rotated before MFA (multi-factor authentication) completion and before protected app access continues.
Inactive users are signed out and cannot regain app access until an Admin makes them active again.
Forgot-password requests send a one-time password reset email for active accounts without revealing whether the submitted email address exists. After a request, the browser shows the same dedicated Check your email page for every submitted address. A successful reset requires the current password policy and rejects the last ten passwords. Success invalidates other outstanding reset links, shows a dedicated Password changed confirmation, and continues to the required MFA challenge or setup. Authentication forms identify the account email as the password-manager username and provide compatible password-generation rules. Optional show and copy controls remain available in the collapsed password-manager help.
New signup accounts must verify their email address before app access. Sign-in, password recovery and MFA setup remain unavailable until the address is verified. The Verify your email page can resend a fresh link for the pending account.
Magic-link sign-in sends a one-time email link to active, email-verified user accounts only. The browser receives the same confirmation message whether or not an account exists for the submitted email address.
Multi-factor authentication is enforced before app access. After password or magic-link verification, users must either set up authenticator-app TOTP (time-based one-time password) or enter their existing six-digit authenticator code. First-time setup shows a QR code and the manual setup key. Users may open a restricted preview of their first onboarding steps while setup is pending, but it contains no account data.
Roles
Create and maintain permission sets for least-privilege access.
The Roles list supports status filtering plus sorting by name, code, status, and created date.
Admin role detail includes a collapsed Record change history card for record-level audit events on the role record.
Support requests
Review lightweight in-app support requests from signed-in users in the current customer workspace.
Admins can tag each request by status and category. Use Missing AI assistant answer, Missing docs, and Confusing UI categories as curated improvement signals for the AI assistant guidance, documentation, and product polish. Request text is never fed into the AI assistant automatically.
The ChannelWeave team triages requests in a separate internal queue. The customer admin queue only ever shows requests from your own workspace.
Events
Review admin and system activity history.
Use Outcome to show all events or only unresolved operational failures. The Event type and Entity type dropdowns contain values recorded for the current customer, so internal event codes do not need to be typed manually. Range limits the event window. Control Centre error actions preserve their selected range and open this list with Operational failures already applied.
The Time value opens the event detail page. Event type badges are labels, not links. Warning-like rows are highlighted with a warning badge and left-hand accent. When the event-type and warning badges wrap at narrower widths, they stay aligned from the same left edge. The User column shows the team member name when the event is linked to a user rather than exposing the internal user UUID.