← Back to Technical blog

Technical article

From Local Branches to Headquarters: How HENGSHI Supports Tiered Financial Data Access, Masking, and Auditing

A local bank branch needs to view its own operations, a regional branch needs to see its assigned institutions, and headquarters roles have distinct scopes. Job responsibilities also determine whether staff should see identifiers such as phone or identity numbers. Reusing analytics across these levels requires deciding who can see each dataset, how sensitive fields should appear, and what evidence access and export operations leave behind.

Nov 19, 2026Technical blogHENGSHI10 min read
Financial servicesData accessAudit

Article body

Full article

A local bank branch needs to view its own operations, a regional branch needs to see its assigned institutions, and headquarters roles have distinct scopes. Job responsibilities also determine whether staff should see identifiers such as phone or identity numbers. Reusing analytics across these levels requires deciding who can see each dataset, how sensitive fields should appear, and what evidence access and export operations leave behind.

Founded in 2016, HENGSHI pioneered a new generation of Agentic BI for the era of Data+AI. Its integrated portfolio brings together the HENGSHI SENSE enterprise analytics platform, HENGSHI JARVIS super digital employees, the HENGSHI CLI execution engine, and HENGSHI BOX, a control hub for private deployments. With a decade of BI experience, HENGSHI supports software vendors across industries through its Powered by Hengshi ecosystem. It provides integrated, end-to-end AI analytics within trusted private environments for operations management and data-driven decision-making at enterprise groups in manufacturing, finance, retail, government, and other sectors.

1. Reuse one dashboard with views suited to each role

1.1 Organizational scope and job responsibilities

Headquarters can maintain a common operating dashboard. Regional and local branches reuse it within their authorized areas. Headquarters accounts should receive customer-level details only when their responsibilities require them. Operations analysts, risk staff, and customer service staff can have different needs for the same fields. Design scopes around both institution and role.

Example roleExample data scopeExample field and export policy
Local branch analystAuthorized branch and outletsPrefer aggregates and masked identifiers. Allow export when the role needs it
Regional managerAuthorized institutions in the regionCompare operating metrics. Grant customer detail and sensitive fields separately
Headquarters project analystInstitutions covered by the specific assignmentGrant necessary fields for the task. Keep the object, volume, and operation record available for review

The table illustrates possible designs. The institution should decide the actual scopes without assuming that branches can see full phone numbers or that headquarters can export all data by default.

1.2 Agree on metrics before aggregating institution data

Operating scorecards, managerial summaries, and financial statements may use different definitions. Business and finance teams should agree on internal transactions, cost allocations, and eliminations before implementing them in metrics and models. HENGSHI can store definitions, filters, and dimensions. A financial consolidation requires the correct business rules in addition to an organizational rollup.

2. Configure application, row, column, and feature permissions

2.1 Map users to authorized institutions

The organization tree describes headquarters, regional branches, local branches, and outlets. Assignment to a node does not automatically authorize access to all data in its descendant institutions. Maintain explicit mappings between users, roles, institution codes, and authorized scopes, then translate those scopes into query rules. Update and review the mapping after a transfer, concurrent assignment, reorganization, or temporary grant expiry.

2.2 Limit rows and columns separately

HENGSHI SENSE supports simple and expression filters for row permissions. Some conditions can reference user attributes. Column permissions restrict field visibility. Set the application’s data permission mode first. Identify whether it applies the application author’s, dataset author’s, or viewer’s data permissions and where the corresponding rules are maintained.

Multiple row rules for the same user and dataset combine as a union, so an added rule can broaden access. Row permissions on an upstream dataset do not automatically propagate to a newly joined dataset. Configure that dataset separately. Include both cases in tests with representative accounts.

2.3 Verify viewing, editing, and exporting

An operational dashboard viewer may have different rights to edit applications, publish content, and download customer details. Configure application roles and feature permissions and use HENGSHI security policies for data exports. In portals and API integrations, verify the identity and authorization context actually passed through. A shared privileged account would substitute its broader data scope for the actual user’s.

3. Govern hidden and masked fields

3.1 Field visibility and masking serve distinct purposes

Column permissions determine field visibility. Masking determines the form a visible value takes. A controlled data preparation layer can generate masked phone numbers or pseudonymous customer identifiers for analytics. Configure access to those derivative fields in HENGSHI. When both forms exist, restrict access to the original phone number. Hiding the raw field on the dashboard alone leaves other access paths open.

3.2 Check the data before it reaches the browser

A browser mask still leaves the original value in the response if it is applied only after delivery. Verify actual query results, detail views, filter options, API responses, and embedded displays. Document whether original values are needed, who can see them, and which data layer applies masking. Treat these decisions as part of project design and acceptance.

3.3 Verify watermark and scope for each export format

HENGSHI can restrict export rights and set export row limits. When watermark protection is enabled, system pages and PDF, PPT, and PNG exports can include details such as username and time. Those formats define the stated watermark coverage. For data exports such as Excel detail files, check the export authorization, fields, row count, and operation record.

4. Use system logs and meet additional audit requirements through implementation

4.1 Inspect the actor, object, and outcome

HENGSHI SENSE operation records include time, operator, IP address, action, result, category, object, and description, with filters and search. Filter for “Export data” to inspect the downloaded object and data volume for detail exports and aggregated Excel exports. This gives administrators a concrete entry point for investigating access and exports.

4.2 Specify field-level tracking and log integrity separately

Some institutions require query conditions, accessed fields, a related approval number, or centralized logging. Confirm the coverage of the current logs and how any additional events are captured. Set retention, access, backups, integrity safeguards, and alerts in the deployment and operating design. An operation log alone cannot establish that the full set of audit requirements has been met.

4.3 Validate a complete record from the actual entry point

Use a representative role to open the dashboard, query an authorized institution, and perform an allowed export. Verify the exported file’s fields and row count, and check the corresponding system operation record. Check access to an institution and field outside the role’s scope and verify that the request is refused or the result is limited. Include the portal, embedded view, or API actually used in production.

5. Introduce shared analytics into daily operations

5.1 Start with one dashboard and one organizational chain

Choose representative roles at headquarters and at each branch level. Align metrics and organization codes, configure application, data, and export permissions, then check operation records. When adding an institution, reuse the verified models and applications and check new user mappings, dataset rules, and entry points.

5.2 Give external partners their own authorization boundaries

Where the project calls for it, use HENGSHI tenant spaces to grant selected resources and let partners analyze within their own space. Design authentication and resource authorization separately. Tenants, user identities, and data rules together determine what each partner can access.

5.3 Carry the same limits into Data Agent

With natural-language access, validate that the same user sees the same authorized data scope in dashboards, questions, and tool calls. Limit callable operations to those appropriate to the role. A user authorized to see aggregates should continue to receive only aggregates through the conversational interface.

6. Make shared analytics usable and auditable

HENGSHI provides metrics, analytics apps, row and column permissions, export controls, watermarks, and operation records. The institution maps those capabilities to its organization, job responsibilities, and governance rules. Each role can use the shared dashboard within its scope, and reviewers can inspect the evidence left by important operations.

HENGSHI SENSE

Resources, ecosystem, and implementation stories

Explore how teams design and ship analytics with HENGSHI.

Request a trial

Enterprise deployment, embedded delivery, and trial requests can all be handled quickly.