System Administration Overview

Page Guide

ScenarioFor platform administrators initializing organizations, accounts, roles, menu permission, data scope, and system parameters.

PrerequisiteThe platform is deployed and an administrator account is available. Organization hierarchy and role boundaries have been planned.

PathSystem Management -> Department / Organization -> Role -> User -> Menu -> Dictionary -> Parameter.

1. Initialization Order

2. Organization And Department

Organizations are the foundation of tenant management and data isolation. In a formal project, finish organization planning before importing devices and users.

Organization management

Field	Description	Notes
Organization name	Enterprise, project, customer, or department name.	Use a business-readable name.
Parent organization	Builds hierarchical data management.	Parent roles may view child data depending on permission.
Administrator	Administrator of the current organization.	Each organization should have a clear owner.
Invitation code	Used when Web registration binds to an organization.	Use together with role permission.
Status	Enabled or disabled.	Disabling affects child users.

3. Roles And Data Scope

Roles decide which menus, buttons, and data a user can access.

Role management

Data Scope	Scenario
All data	Super administrator or platform operations.
Current organization and below	Regional administrator or group administrator.
Current organization	Single tenant administrator.
Own data only	Ordinary business user.
Custom data	Special projects or cross-organization collaboration.

Warning

Device, product, scene, work order, report, and other modules may all be affected by data scope. When a page has no data, check role data scope as well as APIs.

4. User Management

User management

When creating users, confirm organization, role, contact information, status, and password policy. Terminal users are usually used by App or mini-program device binding, while tenant users are used for Web console management.

5. Menu And Button Permission

Type	Purpose	Example
Directory	Left menu grouping.	Device Management.
Menu	Accessible page.	Product Management, Device Management.
Button	Page-level operation permission.	Add, delete, export, command delivery.
External link	Link to an external system or dashboard.	Visual dashboard or online demo.

After modifying menus, re-authorize roles and ask users to log in again for verification.

6. Dictionaries And Parameters

Type	Example	Notes
Dictionary type	Alert level, card platform, notification business code.	Changes may affect frontend display and backend enum mapping.
Dictionary data	Enabled/disabled, level, platform type.	Keep keys stable for historical data.
System parameter	Login setting, business switch, third-party key.	Confirm whether restart or cache clearing is required.
Translation config	Menu, dictionary, and thing-model translations.	Maintain together for multilingual scenarios.

7. Acceptance Checklist

Item	Expected Result
Organization	Parent-child relationship is correct.
Role	Menu, button, and data scope match expectations.
User	Different users see different menus and data.
Data isolation	Unauthorized parent or sibling data is hidden.
Command permission	Only authorized users can deliver device commands.
Audit	Login logs and operation logs are traceable.

Related Docs

• Tenant Management
• Platform Module Matrix
• Backend Module Map