Published at: 2026-09-17
Organization structure and account model
Learn how the platform manages enterprise administrative hierarchies and employee accounts.
Overview
The Org Structure supports business processes and permission control. The platform defines clear administrative levels, including companies, organizations, and departments, together with a standard account model. This gives you a people and data foundation for complex business operations.
Core concepts
The platform supports the following organization levels and member relationships:
| Administrative level or member role | Definition | Permission and business behavior |
|---|---|---|
| Headquarters | The top-level administrative node. | The default top-level node. You can customize its name. |
| Organization | An entity created after you enable multi-organization management. | Use it for subsidiaries or independent business units. Data permissions can be isolated by organization. |
| Department | A child node under an organization or parent department. | Departments form a hierarchy. By default, a parent department manager can view data in child departments. |
| Primary department | The one primary administrative department to which an employee belongs. | The system uses this department to identify the approver in approval and business processes. |
| Secondary department | One or more supporting departments to which an employee is assigned or related. | Use secondary departments for cross-department collaboration. You can assign multiple secondary departments. |
| Manager | The employee’s administrative reporting manager. | The basis for hierarchical data permission inheritance. A manager inherits access to subordinate records by default. |
Organization hierarchy model
With the standard configuration, the organization tree contains only department levels. When an enterprise grows and has multiple subsidiaries or independently accounted entities, you can enable multi-organization management.
graph TD
A["Headquarters (top-level node)"] --> B["Subsidiary or organization A (multi-organization level)"]
A --> C["Subsidiary or organization B (multi-organization level)"]
B --> D["Child department A1"]
B --> E["Child department A2"]
D --> F["Employee 1 (primary department A1)"]
E --> G["Employee 2 (primary department A2)"]
C --> H["Child department B1"]
[!NOTE] After you enable multi-organization management, the system automatically upgrades the root department to an organization node. You can create child organizations and departments under an organization, but you cannot create an organization under a department. You cannot disable this capability after enabling it.
Account and employee attribute model
A complete employee account contains the following three information groups:
- Account information:
- System Nickname: The unique identifier for an employee in the system. It cannot be duplicated and supports multilingual display.
- Name: The employee name registered in the system. Duplicate names are allowed.
- Login account: The personal account used when the employee signs in with an enterprise account.
- Single Sign-On Account: The account identifier used for Single Sign-On (SSO) with a third-party identity provider, such as WeCom, DingTalk, Feishu, or an external IdP.
- Organization relationships:
- Primary and secondary departments: Define the employee’s administrative and business affiliations.
- Reports To: Defines the administrative reporting line and helps the system identify approvers and inherited data access.
- Roles:
- The employee’s business roles, such as sales representative and sales manager, and management roles, such as system administrator and organization administrator.