Users and Admin Permissions

Create Accounts and Invitations

Use registration invitations in the admin panel to create a user or generate a registration link. The initial administrator is created during deployment setup; ordinary users join through invitations.

Assign Admin Permissions

1. As a super administrator, open permission groups and create a group.
2. Select the required capabilities and save.
3. Choose the group in the action area on the right of the user list and confirm.
4. Sign in as that user to verify available menus and actions.

Delegated administrators operate on unprotected ordinary accounts within their permissions. Super administrators handle password resets, authorization, security settings, and complete diagnostics. Chat access follows conversation membership and ownership.

Disabling a group or revoking permissions affects subsequent admin requests from existing sessions. Review existing invitations and bridge settings separately.

Ban and Restore Users

Choose a ban action from the user list. Select permanent or enter a duration in days, hours, or minutes. Temporary bans expire automatically without manually running a scheduled task.

For a forgotten super-admin password, follow account recovery.

View Login Records

Open user details to see the latest three successful logins, including time, source IP, browser, and operating system. The newest record is expanded; older records are collapsed. New records replace the oldest.

Web sign-in makes a brief STUN probe and associates WebRTC addresses with that login. Source IPs may be proxy exits; WebRTC and browser details are client-reported troubleshooting data. Document collection purpose, scope, and retention in your site's privacy policy.

Personal Profiles

Users edit display name, avatar, and bio in personal settings. Bios support up to 200 Unicode code points, line breaks, and clearing. Signed-in users can open profiles from chat avatars.

Telegram and other external profiles show information already available in messages.

Upgrade an Older Site

Actions applies permission and login-history migrations automatically. Historical full-access administrators map to super administrators once; repeated deployments preserve groups and permissions. Custom forks with different is_admin semantics should review the permission migration guide first.