Published at: 2025-10-30
Data Permission Troubleshooting Guide
1. Troubleshooting Common Data Permission Issues
1.1 Permission Exception Troubleshooting Process
- First use the Data Permission Query Tool for initial diagnosis
- If the issue persists after initial checks, submit a bug report to the development team for deeper analysis
1.2 Data Visibility Issues
Related Teams Member Permissions
- Department Member View Permissions
- Employees have read-only access to data only when their primary Dept. or secondary Dept. is a sales Dept.
- Employees in sub-departments of a sales Dept. do not have data view permissions by default
- Account Data Special Notes
- Account Pool records (no owner) are not visible to Related Teams members by default
- To view these records, request enabling the corresponding feature flag
Department Management Permissions
- Dept. Head and Assistant Permission Scope
- They can view and edit only data owned by the Dept. they manage
- Permissions depend on the data’s owning Dept., not on the Dept. of the data owner
- Verify whether the data’s owning Dept. falls under the Dept. head’s jurisdiction
- When a Dept. is deactivated, the system automatically revokes data permissions for the Dept. head and assistant
2. Data Sharing Related Issues
2.1 Owner-based Data Sharing
- Data Sharing Prerequisite
- Records must have an assigned owner; records with no owner are not shared
- Target Dept. Access
- Only direct employees of the target Dept. can see shared records
- To allow access to child Depts., enable the “Include Sub-departments” option
2.2 Dept.-based Data Sharing
- Sharing Restrictions
- Records belonging to deactivated Depts. will not be shared
- Access Permissions
- Only direct employees of the target Dept. can see shared records
- Grant access to child Depts. by enabling the “Include Sub-departments” option
2.3 Condition-based Data Sharing
- Data Sharing Effective Time
- After enabling or disabling a sharing rule, changes typically take effect within approximately 2 hours; actual time varies with data volume
- Account Data Sharing Special Notes
- Accounts without an owner are excluded from condition-based sharing by default
- You can request approval to enable sharing of ownerless records
- External Condition Sharing
- If an Account’s external owner is empty, external-condition sharing will not apply
- You can request approval to enable sharing of records without an external owner
3. Special Object Permission Notes
3.1 Sales Records
- Sales records follow an independent permission handling logic
- For permission issues, contact the Social team
3.2 Contract Object
- Contracts in a non-effective status do not support owner changes
3.3 Refund Object
- Editing rights for records in Refunded status are limited to:
- the owner
- the owner’s manager
- administrators
3.4 Sub-object
- Permissions inherit from the Primary Object
- Sub-objects do not appear separately in Data Permission Management
3.5 People Object
- CRM administrators do not receive default access
- Grant access explicitly via Data Sharing or other authorization mechanisms
4. Temporary Permission Notes
- Temporary permission rules apply only to new records created after the configuration
- They do not apply to workflow nodes or records that circulated before the configuration
5. Common Issue Solutions
| Issue Type | Solution |
|---|---|
| Account Pool records not visible | Request enabling the feature flag |
| Sharing of ownerless records | Request approval to enable special permission |
| Access to department sub-level data | Enable the “Include Sub-departments” option |
| CRM administrator permissions | Grant via Data Sharing |
Notes
- Before making permission changes, confirm the record status
- For special permission requests, follow the formal approval process
- After modifying permission configurations, perform validation tests
- For complex permission issues, contact Technical Support