Open a document room for the other side’s advisers — with a projection, a guest list and an end date.

Business situation

A London law firm acts for the seller of ABC Limited. The buyer’s solicitors and accountants need to review the company’s contracts, leases and employment documents during due diligence. The firm must share exactly the documents the seller has agreed to disclose, for as long as the process lasts, and no longer.

Why existing tools alone are insufficient

Shared folders are easy to over-share and hard to close. A link sent in an email keeps working after the deal falls through. And the buyer’s advisers increasingly want to ask their own AI about a large set of documents — which a folder link either blocks entirely or allows without any boundary.

Systems involved

• SharePoint — the seller’s documents, organised by the firm.
• KroyDB — the room entity, its document list, question log and guests.
• The advisers’ own AI — tools the firm does not control.

Kroy architecture

The firm creates a document room Channel carrying a projection of the approved documents only. The buyer’s advisers are invited as guests with an expiry date. Each guest can connect their own AI to Kroy, which acts under the guest’s delegation and is bounded by the room’s projection. The Channel offers two Skills: Answer Due Diligence Question and Raise Request.

Workflow

1. A partner approves the disclosure list. The documents enter the room’s projection.
2. The buyer’s solicitor is invited as a guest, with access ending on the date set by the firm.
3. The solicitor connects Claude and asks: “Which contracts in the room have change of control clauses?” Kroy returns room documents through room.document.read, and Claude answers.
4. The solicitor asks: “Show me the seller’s advice on the dispute with the landlord.” Kroy refuses: that advice is not in the room.
5. The buyer’s accountant, using ChatGPT, raises a question with request.create. The firm answers it with request.respond, and the answer is added to the question log.
6. The expiry date passes. The accountant’s ChatGPT asks for a lease. Kroy refuses: the guest’s access has ended.

Agent permissions

Guests’ AIs can read only the room’s projection and invoke only the room’s Skills, and only while the guest’s access is live. They have no route to the seller’s wider files.

Human permissions

The partner decides what enters the room and when it closes. Guests can read and ask questions. The firm can extend or revoke any guest at any time.

State changes

• Documents are added to the room as they are approved.
• Questions and answers are recorded in the room’s log.
• At expiry, each guest’s access is marked Ended.

Audit outcome

Kroy records every document read, every question, the refused out-of-room request and the refused request after expiry — with the guest, the agent and the policy.

External sharing

This workflow is external sharing. Expiry and revocation stop future access; they cannot recall what a guest has already read, so the room contains only what the seller has agreed to disclose.

Security considerations

• The room’s boundary is the projection, enforced by Kroy on every request.
• The firm does not need to trust or configure the guests’ AI providers.
• SharePoint credentials stay in Kroy; guests never receive links into SharePoint.

Setup requirements

• Microsoft 365 connected to Kroy.
• A room entity and Channel with a projection of approved documents.
• Guests invited with an expiry date.