BI Platform Data Permissions

**The BI platform inherits the data permissions in the business permissions. **

What range of data can I see for the objects involved in the analysis?

• Core objects: The visible data permissions are consistent with the business (consistent with the data seen on the object list page)
• Associated objects: If you can see the data of the core object, you can view the associated object data in the chart, specifically:
  • In the report, it refers to the fields that are visible and configured in the report column, but if you click the main attribute to view the object details, the data permission of the associated object is still used;
  • In the statistical chart, it means that the indicator value after calculating the data of the associated object can be seen, but when viewing the details of the indicator, the data permission of the associated object is still used.
    *** From the object subject (such as the order product subject), data permissions go to the main object. I can see the order, i.e. I can see the order product data. **
    Report administrator: You can view all object data in the chart, including obsolete data (equivalent to CRM administrator).

1. General theme data permissions

Take the customer theme as an example:

• Under Customer Theme Analysis:
  • Customers are the core objects, and contracts, repayments, business opportunities, and sales orders are related objects, so the customer data permissions that can be counted are consistent with the customer list, and in the chart, the business opportunities and order data of these authorized customers can be counted;
  • When viewing the details of the business opportunity amount and order amount indicators, the data authority of the current viewer for this object will still be used.

2. Data permissions for special topics

2.1 Personnel subject data permissions

**Personnel topic data permission control logic is quite special. **

Note: Because there is a multi-association relationship between objects and personnel, the relationship between the person in charge above can also be changed to other personnel relationships in the rules.

Scenario example: Why is the data shared with Amy through the source, but Amy still fails to collect statistics under the personnel topic?

• Scene restoration:
• Department organizational structure: first-level department: Sales Center; second-level departments under the sales center: South China Region and North China Region; third-level departments under the South China Region: Guangzhou Branch and Shenzhen Branch, and North China Region Three-level department: Hebei Branch;

• The administrator shared the business opportunities of the "North China Region" department, the orders and payment returns of the "South China Region" department with Amy, then when Amy was viewing the statistical graph under the topic of personnel, she selected "Share with me", It is impossible to see the data of business opportunity amount, order amount, and refund amount.

• Cause Analysis:

  • Because there is no scope after taking the intersection of the sharing scopes of business opportunities, orders, and payment under the personnel topic;
  • If it is changed to share the business opportunities of "Shenzhen Branch" with Amy, at this time, select "Share with me", and Amy can view the data of the business opportunity amount, order amount, and payment amount of the Shenzhen Branch, because after taking and submitting For the Shenzhen branch.

• Summary: BI is relatively "strict" in the control of the "shared with me" part of the authority. When counting multiple objects at the same time, all indicators can be viewed only when the shared data ranges overlap. Otherwise it cannot be viewed.
  ***Note: Shared "personnel" object data cannot obtain all business data permissions of the associated person, but only the target value and completion value permissions of the person. **

2.2 Department Subject Data Permissions

**Department subject data permission control logic is quite special. **

• It is mainly suitable for roles with relatively large permissions, such as department heads, bosses, administrators, etc.
• Report administrators and CRM administrators can see all department data;
• The person in charge of the department can see the data of the department I am in charge of;
• Department assistants can see the data of the department they are assistants in.

2.3 Data permission of the high seas and clue pool

• When it is necessary to analyze the customer data under the high seas obtained by the employees through the high seas administrator/member status, you can use the specific template "high seas customer statistics" to create report analysis:
  • For reports created by this template, the data permissions that can be viewed are consistent with the "High Seas" list page. When using "High Seas" to filter, the selectable range is also consistent with the range in this list;
  • The same is true for lead pools. You can create a new report through the "Lead Data Summary of Each Lead Pool" template. The viewable data permissions are consistent with the "Lead Pool" list page. When using "Lead Pool" to filter, the selectable range is also the same as this list The range is the same.