Let a client ask their own AI about their accounts — without seeing your internal notes.

Business situation

A practice shares ABC Limited’s year-end work with John, its director. John already uses Claude for his own business and would rather ask it than log into another portal.

Why existing tools alone are insufficient

Emailing documents loses track of what has been shared. A traditional client portal requires John to learn another interface. Giving John’s AI access to the practice’s systems would expose everything behind the client record.

Systems involved

• KroyDB — the ABC Limited client entity, its requests, deadlines and approved reports.
• John’s Claude — an AI the practice does not control.

Kroy architecture

The practice creates an ABC Client Channel carrying the ABC client projection. John is invited as a guest with the Client role. John connects his own Claude to Kroy as himself; Kroy treats it as an agent acting under John’s delegation, bounded by the guest projection.

Workflow

1. The practice shares the ABC Client Channel with John.
2. John creates a Kroy account and connects his Claude.
3. John asks: “What records are still outstanding?” Claude receives the client-visible requests and answers.
4. John asks: “What do the practice’s internal notes say about us?” Kroy denies the retrieval: internal notes are not in the projection.
5. John uploads the missing bank statements through documents.upload. The practice is notified by a request.responded event.

Agent permissions

John’s Claude can read only the ABC client projection and invoke only the Channel’s Skills. It has no route to anything else in the practice.

Human permissions

John holds the Client guest role for ABC Limited, with an expiry date set by the practice. The practice can revoke access at any time.

State changes

• The outstanding request is marked as responded.
• The uploaded documents are attached to ABC Limited.

Audit outcome

Kroy records John’s access, his agent’s requests, the denied retrieval of internal notes and the upload.

External sharing

This workflow is itself external sharing. Revocation stops future access; information John has already seen cannot be recalled, so the projection contains only what he needs.

Security considerations

• The boundary is the projection, enforced by Kroy — not an instruction to John’s AI.
• The practice does not need to trust or configure John’s AI provider.

Setup requirements

• A client entity for ABC Limited in KroyDB.
• A client Channel with a projection that excludes internal fields.
• John invited as a guest.