Published at: 2025-10-30
BI Platform Feature Management
BI Platform Feature Permissions control menu access based on the viewer’s authority, including:
| Menu | Visibility Conditions |
|---|---|
| Reports | Requires at least one visible chart (controlled by combined “View” permissions at both Subject Area and Chart levels) |
| Data Dashboards | Visible to all employees |
| Subscription Management | Requires “Subscribe” permission for at least one Subject Area |
| Report Permission Management | Requires “Create” permission for at least one Subject Area |
| Report Logs | Only visible to Report Administrators and CRM Administrators |
| Statistical Indicator Management | Only visible to Report Administrators and CRM Administrators |
| Goals | Requires “View List” permission for the “Goal Value” object |
| Goal Completion Status | Visible when the Goals menu is accessible |
I. Chart Operation Permissions
What operations can I perform on charts? - What charts can I create? - What charts can I view? - What charts can I edit/delete? - What charts can I subscribe to/export/forward/share?
1.1 Subject Area Permissions
Chart operation permissions follow the same control logic as business objects - managed through the user’s assigned Roles. BI chart permissions are controlled by functional permissions for Subject Areas assigned to each role.
A Subject Area refers to the analytical scope centered around a core object (previously introduced in Reports and Charts). Each “XX Analysis” entry you see when creating reports represents a Subject Area. Every chart belongs to a specific Subject Area.
Your permitted operations depend on the permissions granted for each Subject Area.
picture coming soon:
1.2 Chart-Level Permissions
How to implement finer-grained permission control beyond Subject Area level?
Use Case:
Amy (executive assistant) has Report Administrator privileges (full permissions for all Subject Areas).
Scott (salesperson) only has View/Edit/Delete permissions for the “Account Analysis” Subject Area.
When Amy creates a “Regional Customer Sales” chart under Account Analysis, Scott can view and edit it.
Solution: Chart-level permissions provide granular control over specific charts:
- View Permissions:
- Public: Visible to all
- Private: Only visible to selected individuals, departments, department heads, user groups, or roles
- Operation Permissions (granted to selected users/groups):
- Edit: Modify chart
- Delete: Remove chart
- Export: Download chart
- Subscribe: Set up subscriptions
- Share: Post to feeds
- Forward: Distribute chart
All permissions require corresponding Subject Area access first
picture coming soon:
picture coming soon:
1.3 System-Preset Report Permissions
The “System-Preset Reports” Subject Area controls all preset chart operations:
- CRM/Report Administrators: Full permissions (View/Edit/Delete/Forward/Export/Share)
- Non-admin Roles: Default View permission (configurable for other operations)
- Note: “Edit” allows saving preset charts as personal copies; “Delete” applies only to these personal copies
picture coming soon:
picture coming soon:
1.4 Statistical Indicator Management Permissions
The “Statistical Indicator Management” Subject Area controls permissions for chart subjects and metrics:
| Permission | Description |
|---|---|
| View | Access to management page; view all subjects/indicators |
| Create | Create new subjects/indicators (auto-includes View) |
| Edit | Modify all subjects/indicators |
| Delete | Remove subjects/indicators (auto-includes View/Disable) |
| Enable | Activate subjects/indicators |
| Disable | Deactivate subjects/indicators |
Note: View permission shows unused indicators; Disable permission can deactivate them; Delete+Disable can remove unused indicators
picture coming soon:
II. Dashboard Permissions
2.1 Custom Dashboard Backend Permissions
Dashboard permissions mirror business object controls through Role-based “Dashboard Permissions”:
| Permission | Scope |
|---|---|
| View | Access dashboards |
| Create | Build new dashboards |
| Edit | Modify dashboards |
| Delete | Remove dashboards |
Applies only to custom personal dashboards
picture coming soon:
2.2 Preset Dashboard Backend Permissions
Preset dashboard controls follow the same Role-based model:
| Permission | Scope |
|---|---|
| View | Access preset dashboards |
| Edit | Modify preset dashboards |
| Delete | Remove preset dashboards |
Applies only to preset personal dashboards
picture coming soon:
2.3 Dashboard Page Permissions
Dashboard Types (selected during creation): - Personal: Created by users with Create permission - Enterprise: Only CRM/Report Administrators
View Permissions: - Public: Visible to all with View permission - Private: Restricted to specified users with View permission
| Type | Creators | Data Permissions |
|---|---|---|
| Personal | Users with Create permission | Follow viewer’s data permissions |
| Enterprise | CRM/Report Admins only | Follow admin’s data permissions (with filters) |
Operation Permissions:
| Operation | Rules |
|---|---|
| Create | Personal: Users with Create permission Enterprise: Admins only |
| Edit | Personal: Owners + shared-with (if permitted) Enterprise: Admins edit all |
| Delete | Personal: Owners + shared-with (if permitted) Enterprise: Admins delete all |
| Share | Personal dashboards only |
| Authorize | Enterprise dashboards (Admins only) |
| Hide | Personal customization (affects only user) |
picture coming soon:
- Dashboard Management access restricted to CRM/Report Admins
- Employees see dashboards from: admin assignments, personal creations, shared/authorized dashboards, and new preset versions
- Admin assignments override personal customizations
- Employees can further adjust assigned dashboards (hide/reorder)
- When qualifying for multiple permission sets, the first matching set applies
picture coming soon:
III. Object/Field Permissions
BI Platform inherits business permissions - visible objects/fields match operational permissions.
Example: Salesperson Amy lacks “View List” permission for Payment Collection object:
1. Cannot select Payment Collection when creating reports
picture coming soon:
-
Cannot view details in Payment Collection-based reports
picture coming soon: -
Cannot view Payment Collection fields in associated reports
picture coming soon: -
Cannot view all fields in chart metric details
picture coming soon:
If Amy has object permission but lacks field-level access (e.g., “Total Payment Amount”):
- Field unavailable during report configuration
picture coming soon:
- Field masked (*****) in reports and chart details
picture coming soon:
Special Objects without independent permission controls: - Business Process Instances/Tasks - Approval Process Instances/Tasks - Pipeline Stages - Behavior Point Details
These become available when: 1. The enterprise has corresponding module licenses 2. Active process definitions exist
picture coming soon: