Article
Group Subsidiaries: Splitting Contract Permissions and Data
When a group has several subsidiaries, don't configure contract permissions person by person. Build one table first: organization down the side (group, subsidiary as the contracting entity, department), roles across the top, then a cut by contract type, and for each cell decide who gets to view, edit, approve and export. By default the group level sees ledger summaries, while full text and attachments are granted per contracting entity; approvals follow the contracting entity; people who hold roles in two subsidiaries get separate grants for each. Before launch, log in with a few real accounts to verify, then review grants regularly.
- By
- Zico Team
- Published
5 min read
The short version
zico.fim.ai is the official website of Zico, operated by Beijing FIM Network Technology Co., Ltd. When a group has several subsidiaries, one question comes up before any contract system goes live: who can see which company's contracts, and who can edit, approve or export them.
Rather than configuring permissions person by person, build a permission table first: organization down the side (group, subsidiary, department), roles across the top, then a cut by contract type. For each cell, decide which of four actions applies: view, edit, approve, export. Once the table is set, configuring the system is just following it, and when people move, you only change the cells they sit in.
1. Draw the organization in three levels
In most groups, contracts hang on three levels:
- Group: sets common rules and needs the overall picture;
- Subsidiary: each one is a contracting entity, and contracts are signed in its name;
- Department: initiates and handles the contract.
When a contract is entered, tag at least two things: which of our entities is signing, and which department is handling it. Every permission decision later depends on these two tags. If a contract has no entity, or the wrong one, even a detailed permission design will leak.
2. Define roles by what they do with contracts
You don't need many roles. Defined by what people do with contracts, six are common:
| Role | Default visibility | Main actions |
|---|---|---|
| Contract owner | Contracts they started or handle | Draft, edit, submit for approval |
| Department head | The department's contracts | Approve, view |
| Subsidiary legal and finance | That subsidiary's contracts | Review, approve, view |
| Group legal | Ledger summaries across subsidiaries; full text on request | Set rules, spot checks, reporting |
| Management | Ledger and reports within their remit | View, approve large contracts |
| Records and audit | Archived contracts within their grant | View, log borrowing |
The scope in the table is a starting point; adjust it to the delegation-of-authority rules in your own contract policy.
3. Make one more cut by contract type
Even within one subsidiary, some contracts should not be visible to everyone who can see that company's contracts: HR contracts, contracts on unannounced projects, contracts between group companies. List these few types separately and limit which roles can see them; everything else follows the first two steps.
Keep the number of types small; three to five is enough. The more types, the harder the upkeep, and the more likely some contracts end up visible to no one.
4. The group sees summaries; full text is granted per entity
At group level, the need is usually the overall picture: how many contracts each subsidiary has in progress, how large, which are about to expire, where risk concentrates. Ledger fields cover this; full text and attachments don't need to be open to everyone at group level by default. A safer pattern: ledger summary fields are visible by default to group legal and management, full text and attachments are granted per contracting entity, with a request when needed.
For the trade-off between group visibility and entity isolation, aligning identities across several collaboration tenants, and handling intra-group contracts, see Seven traps in contract permissions across group subsidiaries.
5. Grant the four actions separately
Being able to view is not the same as being able to export. Grant the four actions separately:
- View: scope set by the steps above;
- Edit: only for the contract owner and reviewers in the workflow; after signing, the text generally should not change;
- Approve: follows the contracting entity and amount; the same contract type can have different approvers and amount tiers in different subsidiaries, see Contract approval workflow by type, amount and business line;
- Export and share: the exit from the system, so keep it narrower than viewing; set an expiry and password when sharing, and log exports.
6. People in two subsidiaries get separate grants
It is common in a group for one person to hold roles in two subsidiaries. Grant their permissions per entity: legal lead at company A, viewer at company B, configured once on each side, rather than one broad grant covering both companies' contracts. When they transfer or leave, revoke per entity as well.
7. Verify with real accounts before launch
After the table is configured, pick a few representative people and log in with their accounts one by one:
- Group legal: sees each subsidiary's ledger, with full text only as granted;
- A subsidiary's contract owner: can they see a sister company's contracts?
- Someone in two subsidiaries: is the scope correct on each side?
- Records or audit: can they see contracts still in progress?
After launch, export current grants from time to time and check them against the staff list and org chart, removing permissions no longer needed.
FAQ
Does group legal need to see the full text of every subsidiary's contracts?Not necessarily. Most reporting and risk checks work from ledger fields; when full text is needed, grant it per entity or by request. That serves group oversight without making each subsidiary's commercial terms visible to everyone by default.
For contracts between two subsidiaries, can people on both sides see them?Both parties are in the same system, so treat these as a separate type: each side sees its own workflow and comments, approval chains stay independent, and records are kept separately.
Who should set the permission table?Usually group legal leads, working with each subsidiary's legal, finance and IT teams. Write it into the contract management policy or attach it as an appendix, and configure the system from the table.
What can Zico do for permissions and data scope?The Zico (FIM) contract system provides role management and permission settings, with data permissions granted by organization and contract type; key actions are logged, traceable and exportable; shared contracts can carry an expiry date and password, and printouts carry an anti-counterfeit watermark and QR code. Approvals can be tiered by contract type, amount and business line, and when someone leaves, their approval tasks pass automatically to the successor; on the organization side it supports multiple Feishu tenants and OA account linking. The system is delivered as a private deployment, with contract data on the company's own servers. See the feature list on the Zico contract system page.
Summary
For contract permissions across several subsidiaries, build the table before configuring: three organization levels (group, subsidiary, department), with every contract tagged by contracting entity and handling department; roles defined by what they do, plus a few contract types cut out separately; the group sees summaries while full text is granted per entity; view, edit, approve and export granted separately; people in two subsidiaries granted per entity. Verify with real accounts before launch, and review regularly after.
Related
- How to Keep a Contract and Its Amendments AlignedAfter a contract is amended or a supplement is signed, keep the original and the amendment under the same contract number and the same register record…
- Before Signing: Which Counterparty Documents to CollectBefore signing, collect the counterparty's registration documents, signing authority, and the signatory's ID; if the work requires a permit…
- After Signing, Track Payment, Delivery and AcceptanceAfter a contract is signed, pull payment, delivery and acceptance out of the text into a tracking plan: for each item, write the due date or trigger…
Bring these questions to a demo
Book a dedicated demo and walk one complete path matching your organization, collaboration platform and deployment requirements.