Published at: 2025-10-30
Data Permission Troubleshooting Guide
1. Common Data Permission Troubleshooting
1.1 Permission Exception Investigation Process
- First, use the data permission query tool for preliminary investigation
- If the issue persists after investigation, submit a bug report to the R&D team for in-depth analysis
1.2 Data Visibility Issues
Related Team Member Permissions
- Department Member View Permissions
- Employees only have read-only access to data when their primary or secondary department is the sales department
- Employees in sub-departments of the sales department have no data view permissions by default
- Account Data Special Notes
- Account Pool data (without an owner) is invisible to related team members by default
- To request view permissions, apply to enable the corresponding beta feature
Department Management Permissions
- Department Head and Assistant Permission Scope
- Can only view and edit data belonging to their responsible department
- Permissions are unrelated to the data owner’s primary department, only related to the data’s assigned department
- Verify whether the data’s assigned department falls under the department head’s jurisdiction
- When a department is deactivated, the system automatically revokes data permissions for the department head and assistants
2. Data Sharing Related Issues
2.1 Owner-Based Data Sharing
- Data Sharing Prerequisites
- Data must have a designated owner; data without an owner won’t be shared
- Target Department Permissions
- Only visible to direct employees of the target department
- To make it visible to sub-departments, check the “Include Sub-departments” option
2.2 Department-Based Data Sharing
- Sharing Restrictions
- Data from deactivated departments won’t be shared
- Access Permissions
- Only visible to direct employees of the target department
- Sub-department access requires enabling the “Include Sub-departments” option
2.3 Condition-Based Data Sharing
- Data Sharing Activation Time
- Data sharing typically takes effect within approximately 2 hours after enabling or disabling, depending on data volume
- Account Data Sharing Special Notes
- Account data without an owner doesn’t participate in condition-based sharing by default
- Request approval to enable sharing permissions for ownerless data
- External Condition Sharing
- Invalid when the account’s external owner is empty
- Request approval to enable sharing permissions for data without external owners
3. Special Object Permission Notes
3.1 Sales Records
- Follow independent permission processing logic
- Contact the social team for permission issues
3.2 Contract Object
- Contracts in non-active status don’t support owner changes
3.3 Refund Object
- Edit permissions for refunded status data are limited to:
- Owner
- Owner’s superior
- Administrator
3.4 Sub-object
- Permissions are inherited from the Primary Object
- Not displayed separately in [Data Permission Management]
3.5 Personnel Object
- CRM administrators have no permissions by default
- Requires separate authorization through methods like data sharing
4. Temporary Permission Notes
- Temporary permission rules only apply to new data after configuration
- Don’t affect node data that existed before configuration
5. Common Issue Solutions
| Issue Type | Solution |
|---|---|
| Account Pool data not visible | Apply to enable beta feature |
| Ownerless data sharing | Request approval for special permissions |
| Sub-department data access | Enable “Include Sub-departments” option |
| CRM administrator permissions | Authorize through data sharing |
Notes
- Verify data status before making permission changes
- Special permission requests should go through formal approval processes
- After permission configuration changes, perform permission verification tests
- Contact technical support for complex permission issues