Account Management
Page Overview
Section titled “Page Overview”Account Management is the control center for managing the platform’s multi-level organizational structure and personnel access permissions. On this page, enterprises can clearly manage all subordinate branches, fleets, or agents through a tree view. It also supports assigning internal employees “login accounts” with independent permissions, and creating “regular users” for external personnel who only need to view specific devices, meeting collaborative management needs in complex business scenarios.
Page Features
Section titled “Page Features”Account Tree View and Structure Management
Section titled “Account Tree View and Structure Management”A clear tree topology provides a full view of the hierarchical relationships among the current primary account and all derived sub-accounts at multiple levels. Feature details:
- Add subordinate accounts: Select any node in the tree to create a child enterprise account (for example, a new branch office or downstream agent). Sub-accounts have independent device ownership and management workspaces.
- Account transfer: You can break the original structure and move a subordinate account, together with all its assets and data, to another parent account in the tree. This provides flexibility for organizational restructuring.
Account Information Editing
Section titled “Account Information Editing”Maintain the profile information of specific enterprises or organizations in the tree. Steps: Select the target account and click Edit to modify basic information of the business entity (such as enterprise/department name, contact name, email, and phone number), making business communication and alarm email delivery easier.
Login Account Setup and Permission Assignment (Multi-Account Collaboration)
Section titled “Login Account Setup and Permission Assignment (Multi-Account Collaboration)”This feature is designed for internal collaboration scenarios where multiple employees (such as administrators, dispatchers, and finance staff) need to manage devices under the same account but require different permissions. Steps and logic:
- Create a new account: Select the target enterprise account, click Add Login Account, and set username and password.
- Default permission inheritance: After the account is created, the system automatically grants the same menu permissions as the creator (you).
- Independent permission reset: To enforce internal separation of responsibilities, go to the Login Account List, locate the new account, and adjust its menu visibility permissions (for example, hide Device Management to prevent accidental deletion while keeping Monitoring Center only).
Regular User Creation (End-User Binding)
Section titled “Regular User Creation (End-User Binding)”Used to assign independent login credentials for vehicle owners, drivers, or consumer-side users. Feature details and scope:
- Independent credentials: A regular user is only a login identity with username and password.
- Outside the account tree: A regular user represents an individual, not an enterprise organization entity, so it does not appear in the account tree.
- Weak association: Regular users do not have device ownership. They can only be bound to specific devices. After binding, they can view only assigned devices and cannot perform advanced account management.
Concept Clarification (Important)
Section titled “Concept Clarification (Important)”To avoid management confusion, make sure you distinguish the following three entity levels:
| Entity | Business Meaning | Data and Permission Scope | Appears in Account Tree |
|---|---|---|---|
| Account | Represents an enterprise, branch, or agent entity. | Has independent device ownership, coin balance, and subordinate management rights. | Yes (forms tree nodes) |
| Login Account | The key used to access an account. | Shares device data under its parent account. Supports independent menu permission settings. | No (attached to a specific node) |
| Regular User | Represents an external individual (such as a driver or vehicle owner). | Does not own devices, and can only view specific devices assigned (bound) to the user. | No (outside the tree) |
- Cascading impact of account transfer: When you transfer a subordinate account to another node, all devices, historical data, and child accounts under it are transferred together as one package.
- Regular user creation guideline: If your customer is an enterprise fleet, use Add Subordinate Account. If your customer is an individual owner with one device, directly Create Regular User and bind the device.
Q: A new colleague joined and needs to help monitor alarms. How should I create an account for them? A: Under your current account, use Add Login Account to create a new login for them. Then go to the login account list and keep only monitoring/alarm permissions. Do not use Add Subordinate Account, otherwise they may see an empty account with no devices.
Q: Why can a newly created finance login account see real-time fleet monitoring? A: Because a newly created login account inherits all permissions from the creator by default. Go to the Login Account List, find that finance account, edit permissions, and uncheck menus related to Monitoring Center.