When a customer division moves, what should happen to its old documents?
A portal's organisation selector can make a change look simple: update a company name and move the people. The harder question is which records and permissions should follow the change. Current membership, historical document ownership and permission to share a particular file are separate matters.
This fictional case follows a supplier whose customer division moves to a new legal entity. The example uses a decision supplied by the customer's authorised business and legal reviewers. It does not infer legal ownership from software records or offer a general rule for corporate transfers.
Establish the approved business facts
The original customer organisation is C-11. Its quotation Q-52 and associated file D-52 belong to the historical relationship with that organisation. A division now operates through new entity C-27. Two contacts who worked on the old project will work for C-27 in future.
The approved instruction says that future enquiries from that division should use C-27. It does not authorise moving all C-11 history or making it visible to every C-27 user. A specific request to share D-52 still requires the designated owner's decision.
A proposed shortcut would rename C-11 to the new entity's name and change the contacts' email domains. That would make old quotations appear to have been addressed to C-27. It would also make the meaning of the existing organisation permissions uncertain.
Compare the available models
The project considers three approaches. Renaming the existing organisation is inappropriate because the change is not merely a corrected display name. Copying all records into C-27 would create unnecessary duplicates and imply authority that has not been provided. Creating the new entity while retaining the historical association allows future work to be separated without rewriting the past.
The third approach is selected. C-11 remains the organisation attached to Q-52. C-27 receives its own identifier and approved current memberships. New enquiry Q-73 is created under C-27. The relationship between the organisations can be recorded as context if needed, but it does not itself grant access.
That decision also prevents a misleading search result. A staff member can see which organisation a quotation actually belongs to, rather than finding two copies with different apparent owners.
Decide access record by record where authority is limited
One transferred contact, U-8, no longer has approved access through C-11. Removing that membership should stop future access through that relationship. Their new membership in C-27 does not restore C-11's document library.
The owner later approves sharing D-52 with a specific C-27 role for a defined purpose. The portal records that permission explicitly, including its scope, rather than changing the quotation's original organisation. Other C-11 documents remain unavailable to C-27.
The distinction is important for maintenance. A future editor should be able to tell why D-52 is visible without concluding that every historical document is now shared. A customer organisation's name is not an adequate substitute for a permission record.
Show the resulting checks
The worked review opens Q-52 as an authorised C-11 user and confirms its original organisation and document association. It opens Q-73 under C-27 and confirms the new relationship. A C-27 user with the specifically approved role can retrieve D-52; a C-27 user outside that role cannot. An unrelated C-11 file remains inaccessible to both C-27 test roles.
U-8's removed C-11 membership no longer provides fresh access. Their permitted C-27 work remains available. The review includes direct file requests, not only whether the document appears in a menu.
These outcomes demonstrate the implemented decision in the example. They do not prove that every legal consequence of the organisational change has been resolved. The approved instruction and any unresolved sharing requests remain part of the project record.
Use the case to ask more useful project questions
Before commissioning a portal, ask what an organisation record represents, which changes are simple corrections and which require a new identity. Ask who authorises historical sharing, how permission reasons remain visible and what happens when a person has several legitimate relationships.
Those questions determine more than the account screen. They affect imports, search, reporting, invitations and document retention. A small set of representative cases can reveal the required model before migration turns a convenient shortcut into a lasting ambiguity.
The document-portal service covers implementation of agreed access rules. Project responsibilities explains why the underlying business and professional decisions need authorised owners.