Group companies often need to share material catalogs, but procurement contracts, costs and customer prices may only be viewed by some organizations. Adding an organization field to a table does not automatically create access isolation. The ownership and sharing scope of each type of data need to be defined separately.

How to arrange records and operations

Establish the relationship between organizations, positions and business roles, and distinguish public master data from organizational business records. Lists, exports, interfaces, and attachment downloads all apply the same permissions rules. Cross-organization transactions save the document relationship between both sides and cannot be reconciled by copying the text. Temporary authorization sets clear end conditions.

Shared data also needs to distinguish between read and maintenance permissions. Just because an organization can use public materials does not mean that it can modify the specification definitions of the entire group. Changes to public data should be notified to organizations using the data and outstanding business should be reviewed. When cross-organization administrators handle failures, time-limited authorization can be used to record the purpose and scope of access. Permission acceptance should also check the cache and generated reports: after the account is deauthorized, the old link should not continue to provide data that has lost access qualifications.

Specific scenarios that need to be checked

During the test, use different organizational accounts to query the same materials and different orders, and check whether the search suggestions leak business information. After the job transfer, the access scope is recalculated and the authorization change record is kept. Summary reports make it clear which organizations are allowed to be viewed, preventing the use of totals to reveal unauthorized details.