Share only the context an AI task needs
Choose between an excerpt, a project brief, and a whole-chat handoff based on the information the next assistant actually needs.
Keep a project moving 2 min read
Keep client context separate in AI work
Name the client and project in each brief, use only approved source material, and check the output for details from other work. A naming convention helps organization, but it is not an access-control boundary.
Define what this task is allowed to use
A general instruction to “use what you know” can bring unrelated details into an answer. For client work, give the assistant a short source list and a clear exclusion: do not use other clients’ conversations or examples.
That instruction is a workflow safeguard, not a technical guarantee. If your contract requires isolation, confirm that the tool and account setup provide it. Do not assume a project label, folder, or prompt creates a separate security boundary.
Check the handoff as a disclosure
Before switching providers, inspect the material for names, pricing, unpublished plans, and attached files. A whole-chat handoff may share more than the paragraph you intended to review. Use an approved excerpt when the task permits a narrower scope.
Keep the client’s source of truth outside an unreviewed assistant summary. Record who approved the brief and when. If you cannot establish permission to process the material in a tool, stop at a synthetic example until you can.
TAKE THIS WITH YOU
Client-scoped brief
An illustrative template. Replace the details with material you are allowed to share.
Project: [client-approved label] Task: […] Approved sources for this task: […] Excluded sources: Other clients and unrelated projects. Sensitive fields removed: […] Approved destination: […] Approval owner and date: […] If the approved sources do not answer a question, ask. Do not fill the gap from unrelated work.
USING THIS WITH DRAY
Keep the context. Check the source.
Do not treat Dray’s project context as a promise of client-specific isolation. Confirm the active processing policy before connecting sensitive conversations.
Dray is in beta. Available sources and connections depend on your setup. Read the data notes before granting access.
Sources & next reads
Product details are grounded in the guides below. Example projects and prompts are illustrative, not customer results.