Before You Begin
About This Manual
This manual is intended for the three roles of the All-in-One Platform — System Administrator, Tenant Administrator, and End-User — and systematically introduces the operation methods of each functional module. The manual is divided into three parts by role: Part 1 covers System Administrator operations, Part 2 covers Tenant Administrator operations, and Part 3 covers End-User operations.
Readers are advised to focus on the section corresponding to their own role; System Administrators should read the entire manual to grasp the complete management chain.
Platform Roles
| Role | Abbr. | Responsibilities & Permissions |
|---|---|---|
| System Administrator | SysAdmin | Top-level management authority, responsible for tenant lifecycle management, tenant profile management, tenant admin account management, and platform system configuration. Does not directly manage devices, assets, or end-users. |
| Tenant Administrator | Tenant Admin | Highest authority within a tenant, responsible for user management, device management, asset management, dashboard management, rule chain management, and alarm management under the tenant. |
| End-User | End-User | Basic user permission within a tenant, can only view assigned dashboards, and cannot create, edit, or delete dashboards. Has no rights to manage devices, assets, or rule chains. |
Note: In this document, "System Administrator" and "Super Admin" refer to the same concept — the platform's highest-privilege role.
Account Acquisition
Platform accounts are created and assigned by higher-level administrators. The account sources for different roles are as follows:
| Role | Created By | Initial Credential Acquisition |
|---|---|---|
| System Administrator | Initially created during platform deployment. | The initial account and password are generated at deployment time and received by the deployment lead. If lost, contact platform operations personnel for reset. |
| Tenant Administrator | System Administrator (see 4.1 Create Tenant Admin) | Credentials are assigned by the System Administrator via secure channels (e.g., offline handover, encrypted email). |
| End-User | Tenant Administrator (see 5.1 Create User) | Credentials are assigned by the Tenant Administrator via secure channels. |
Important: The platform does not automatically send initial password emails. All initial passwords are communicated by the creator to the user via secure channels. Please keep them safe and change your password as soon as possible after first login.
Special Note on Rule Chains
Rule Chains are the core engine for data flow and business logic processing on the platform. The system-preset rule chains are relied upon by the platform's basic functions and must not be deleted.
| Rule Chain Type | Description | Deletable |
|---|---|---|
| System-preset Rule Chains | Automatically created during platform initialization, carrying core data processing logic. | No |
| Custom Rule Chains | Custom rule chains created by Tenant Administrators based on business needs to extend data processing workflows. | Yes, but only after confirming that no devices/assets are associated with them. |
Warning: Deleting system-preset rule chains will cause platform malfunctions. Do not operate. Before deleting custom rule chains, ensure all associations with devices and assets have been removed.
Glossary Quick Reference
| Term | Brief Description |
|---|---|
| Tenant | A logically isolated unit on the platform that can contain independent users, devices, assets, dashboards, and data. |
| Tenant Profile | A configuration template defining feature sets, quotas, and module availability for a tenant. |
| Device | Physical or virtual endpoints that connect to the platform and report data. |
| Asset | A logical grouping of devices or other assets for organizing and managing resources. |
| Dashboard | A visual display interface configured with data sources for monitoring and analyzing data. |
| Rule Chain | A data processing pipeline composed of rule nodes, defining how data is ingested, processed, and forwarded. |
| Alarm | Notifications automatically triggered based on conditions configured in rule chains for alerting on abnormal situations. |
| Audit Log | Logs recording critical platform operations for security auditing and issue tracing. |