1. Positioning of System Operational Data

• The purpose of collecting enterprise operational data is to comprehensively capture, intelligently analyze, and manage full‑chain activities. Its value lies in optimizing business operations, forecasting market demand, improving product performance, enabling precision marketing, and evaluating customer value.

2. ShareCRM System Operational Data Capabilities

1. Product capabilities and activation

• The system operational data analytics product includes three objects: Employee Object Behavior Analysis, Employee Login Behavior Analysis, and Employee BI Behavior Analysis. These objects can report and analyze both Upstream and Downstream data.

• Employee Object Behavior Analysis: analyzes action logs across all system standard and custom objects (including flow‑related objects and Sub-object). The specific actions that can be analyzed correspond to the object’s backend “button” list. On the configuration page, you can select all standard buttons. Custom button actions are captured under the “Edit” button; in addition to backend action buttons, the “View Details” action is also supported. Once enabled, the system will collect and analyze View Details events for that object.

  • Flow‑related data follows the business object and requires no separate configuration. When you enable analysis for an object, any flow data generated under that object is included automatically.
  • When you enable the Employee Object Behavior Analysis module switch, the system automatically records menu view data.

• Employee Login Behavior Analysis: captures login events for all login methods (including QR Code Login, dynamic verification code login, and logins via DingTalk/Feishu), as well as online sessions where users are still logged in. Once enabled in the backend, no additional configuration is required to start analysis.

• Employee BI Behavior Analysis: tracks actions on BI resources such as Reports, Joined Report, Chart, Statistic Chart, Dashboards, and Products — including view details, create, and export actions. After enabling in the backend, manually select which BI resource types you want to analyze.

2. Functional description

• Functional permissions: use the backend “User Behavior Analysis” permission module. By default, CRM administrators and Reports administrators have full permissions for this module. Aside from the “View All” permission — which controls whether a user can see all data across all objects in the module — other permissions apply at the Subject domain level and control operational capabilities within that domain.

• Data permissions: by default, the system enforces data access based on Org Structure. Data sharing is not supported except via the “View All” functional permission, which grants access to all objects under this module.

3. Analysis capabilities

• You can analyze behavior data in BI using Chart. Select the Subject object you want to analyze to open the Chart editor and perform analysis.

• Each object includes fields that reference Downstream records. You can base analyses on these fields to examine related Downstream data.

picture coming soon: