Users, Admins, and Permissions

Goal

Create users, administrators, roles, and permissions in the admin console to support site access, group authorization, and collaboration.

Prerequisites

• You are logged in to https://<APP_DOMAIN>/admin/login.
• Your account has permissions for user, admin, role, and permission management.

Steps

1. Go to "User Management > User List" and click "Add User".
2. Enter username, nickname, email, mobile number, password, user type, and status.
3. After saving, edit, delete, or manage login devices from the user list.
4. Go to "User Management > Admin List" to create admin console accounts.
5. Go to "User Management > Role List" to create roles.
6. Go to "User Management > Permission List", select a role, and assign menu and operation permissions.

Field Reference

Field	Description	Recommendation
Username	Login account, usually unique	Use employee ID, email prefix, or a consistent naming rule
Nickname	Display name	Make it easy for admins to identify the person
User Type	Normal or collaboration user	Use collaboration users for external access
Status	Active or inactive	Disable departed, expired, or paused accounts
Role	Controls admin menus and actions	Admin accounts must have suitable roles

Permission Recommendations

Role	Target User	Suggested Permissions
System Administrator	Operations and platform owners	All menus, system settings, license, and logs
Business Administrator	Department or project owners	Users, sites, workspaces, groups, collaboration
Auditor	Security or compliance users	User logs, replay, dashboard
Normal User	Business user	No admin console permissions; access frontend resources through groups

Verification

• The new user can log in to the user portal.
• The new administrator can log in to the admin console.
• Unauthorized menus are hidden from users with that role.
• Disabled users cannot continue logging in or accessing portal resources.

FAQ

• Users access sites and workspaces; administrators manage the backend.
• Collaboration users can access collaboration through personal links.
• Users may need to log in again after permission changes.