Article body
Full article
Enterprise decisions usually begin with a data finding and then move into business discussion, confirmation, and action. HENGSHI enterprise BI supports subscription delivery, threshold alerts, application publishing, permission management, and metric management to help organizations distribute analytical results and manage access to data and metric assets within controlled boundaries. This article stays within publicly described product capabilities and explains the relevant scenarios, configuration considerations, and validation points.
1. Delivery and Management Challenges in Enterprise BI
1.1 Collaboration happens outside the system, breaking the decision trail
A common pattern begins when a business user spots a metric change in BI and shares a screenshot or link in a group chat. Discussions may remain in an external collaboration tool. It is therefore important to keep analytical results, data-access scope, and metric definitions clear so that teams can verify and reuse them later.
1.2 Unclear publishing boundaries make definitions harder to govern
When application publishing scope, interaction permissions, and metric definitions lack a shared convention, departments may interpret the same metric differently. This increases the cost of consolidation and review. Application publishing, data permissions, and metric asset management should be part of normal operations.
1.3 Passive information depends on people watching dashboards
Checking dashboards manually every day can cause important results to be missed. Configurable scheduled subscriptions, immediate delivery, and alerts based on explicit thresholds provide better delivery patterns for different business rhythms.
2. Controlled Sharing: Use Analytical Results Within Authorized Scope
2.1 Application collaboration and authorized viewing
HENGSHI collaboration management can be used to view and adjust application authorization relationships, including applications shared with or by the current user. Application and data permissions can be configured by user, user group, organization, and tenant, with additional controls for rows, columns, and buttons. Business discussions can continue through an enterprise’s existing collaboration tools.
2.2 Published areas and interaction permissions
Publishing an application creates a published snapshot. The published area hides authoring functions, while publishers can configure interaction permissions according to business needs. This boundary separates stable consumption from ongoing authoring, allowing users to view, filter, and use published analytical applications within their authorization.
2.3 Analytical assistance from Data Agent
HENGSHI Data Agent can support on-demand analysis, metric creation, and dashboard generation while retrieving and analyzing only the data a user is authorized to access. AI output is nondeterministic, so consequential business decisions should still be reviewed against metric definitions and source data.
3. Subscriptions and Delivery: Let Information Reach People
3.1 Dashboard subscriptions
HENGSHI supports immediate and scheduled subscriptions through channels such as email, WeCom, Lark, Webhook, and DingTalk. A subscription can include a dashboard snapshot, link, or data. Its contents and frequency should be configured according to business rhythm, recipients, and security requirements.
3.2 Threshold-based metric alerts
Metric alerts are based on explicit thresholds and detection schedules and can be delivered by email or Webhook. They suit clearly bounded risk signals with an identified owner and response process. Metric alerts are currently unavailable in the published-application state, so teams should validate the actual entry point used in their deployment.
3.3 Permission constraints on delivery
Subscription recipients must be reviewed together with application and data permissions. Internal system users follow application data permissions, while external users are handled according to the application author’s permissions. For sensitive data, confirm the visible scope and delivered content during subscription configuration and application authorization; the delivery channel alone does not imply automatic masking.
4. Organization-Level Management: Define Boundaries for Publishing, Permissions, and Metrics
4.1 Application publishing and controlled sharing
HENGSHI application publishing creates a snapshot, hides authoring functions in the published area, and allows interaction permissions to be configured. Enterprises can combine their own publishing review requirements with platform publishing and authorization controls to reduce the risk of unreviewed content entering the usage scope.
4.2 Centralized metric asset management
HENGSHI can maintain metric definitions, descriptions, topics, online status, and lineage, creating manageable metric assets for consistent definitions and impact analysis. For core metrics, enterprise processes should identify owners, record changes, define communication methods, and check affected applications.
4.3 Organizing permission responsibilities
An enterprise can use HENGSHI users, user groups, organizations, tenants, application and data permissions, row and column permissions, and button permissions to divide access and operational boundaries according to its responsibility model. Business responsibilities, publishing checks, and operating roles should be defined by enterprise policies and the implementation plan.
5. Platform Boundaries and Management Support
5.1 Layered permission management
HENGSHI supports application and data permissions across users, user groups, organizations, and tenants, together with finer-grained row, column, and button controls. Published applications, subscription content, and data access should be configured from these actual permission and asset boundaries.
5.2 Resource, behavior, and runtime monitoring
HENGSHI provides resource, user-behavior, and runtime monitoring to help organizations understand platform resource use, user actions, and operating status. The exact relationship among subscriptions, alerts, publishing, and permissions depends on the enabled functions and current product version.
5.3 System operation records and auditing
System operation records can include time, operator, IP address, action, result, category, object, and description, and they support audit export. These records can help with operational management and incident tracing. Compliance applicability must still be assessed against the actual deployment, configuration, and formal evaluation results.
5.4 Tenant-level permission configuration
The permission model includes a tenant dimension that can be combined with users, user groups, and organizations to configure access scope. The isolation model, administrator responsibilities, and management process depend on the deployment and implementation configuration.
6. Implementation: Start With Permissions and Metric Management
6.1 Define permissions and metrics before configuring delivery
Start by establishing definitions, descriptions, topics, and lineage for core metrics. Then define publishing checks and application and data permissions before configuring subscriptions and alerts. This confirms data assets and access boundaries before delivery scenarios are expanded.
6.2 Balance access and control
Business teams need timely information, while sensitive data must remain controlled. HENGSHI can define access scope with application and data permissions and row, column, and button controls. Subscription design should distinguish permission rules for internal and external users and confirm the delivery scope of each snapshot, link, or dataset.
6.3 Begin with a bounded scenario
An enterprise does not need to roll out every capability at once. It can begin with one core operating application, complete metric definitions and permission configuration, and then validate scheduled or immediate subscriptions, published-area interaction permissions, and any necessary threshold alerts. After confirming recipients, response processes, and data scope, it can expand to other business domains.
Table 1. Delivery and Management Capability Overview
| Management dimension | Common manual approach | Basic sharing approach | Configurable HENGSHI capabilities |
|---|---|---|---|
| Information delivery | Manual checking or forwarding | Links, exports, or manual notifications | Immediate or scheduled subscriptions with dashboard snapshots, links, or data through selected channels |
| Risk signals | Depend on manual discovery | Notify after external monitoring | Alerts based on explicit thresholds and detection plans through email or Webhook; currently unavailable in published applications |
| Sharing boundary | Personal files | Shared links or copies | Application and data permissions, including row, column, and button controls, with separate rules for internal and external users |
| Published use | Distribute after individual authoring | Share content for viewing | Publishing creates a snapshot, hides authoring functions, and supports configurable interaction permissions |
| Metric assets | Maintain metrics separately by report | Documented conventions | Definitions, descriptions, topics, online status, and lineage; change impact must be checked through management processes |
| Operations and audit | Difficult to review consistently | Depend on surrounding systems | Resource, user-behavior, and runtime monitoring; auditable and exportable system operation records |
7. Frequently Asked Questions
Will subscriptions and alerts create too much noise?
Subscriptions should be configured by audience, frequency, channel, and content. Scheduled subscriptions fit results that need periodic attention, while threshold alerts fit clearly bounded risk signals. Confirm recipients and response ownership before rollout instead of sending undifferentiated notifications.
Can a published application use metric alerts directly?
Current public product documentation states that metric alerts are unavailable in the published-application state. Risk delivery for a published application should combine subscriptions, external notification processes, and the capabilities of the deployed version, with validation before rollout.
What if subsidiaries and headquarters use different metric definitions?
Core metrics can be managed as governed assets with definitions, descriptions, topics, and lineage. Enterprise processes should specify change responsibilities for headquarters and subsidiaries. Local variants should have an explicit relationship to core metrics and undergo impact checks; the platform should not be assumed to coordinate every definition automatically.
8. Conclusion: Support Decisions With Verifiable Delivery and Management
Enterprise BI presents data, delivers authorized analytical results through suitable channels, and defines boundaries for publishing, permissions, and metric assets. HENGSHI provides configurable capabilities for subscriptions, threshold-based alerts, application publishing, permission management, and metric management.
Implementation should follow public capabilities, the deployed version, and project configuration. Organizations need to define who may use which data, when and how results are delivered, and how metrics are maintained and reviewed. This allows BI to support business decisions on a controlled and verifiable foundation.