Check Data Scope Before Giving Work to an AI Partner

Before giving an AI partner client notes, meeting records, or work files, decide what input it needs, who will handle it, and where the result should appear. Check one small task before using the full work material.

When to use this guide

Use this check before a partner handles work material for the first time, or after changing the partner, channel, or model. For a meeting follow-up task, prepare only the relevant passages instead of submitting an entire folder.

Before you start

Work data stays on your device by default; only channels you connect and model calls go online as the task requires.

Confirm that the material may be used with the selected channel and model. Material stored on your computer still needs a scope check when you use it in an online task. Ask the material owner first if permission is unclear.

1. Define the permitted input

In an ordinary document, record the task, the input it needs, and who may receive the result. For example, extract follow-up items from a meeting excerpt and return them to you for review, without posting to a client group.

Leave unrelated attachments and passages out of this submission. Remove passwords, secret keys, and personal details unrelated to the task from the working copy before continuing.

2. Find the responsible partner

Open AI Partners in the sidebar and find the target partner in management mode. Check its name, role, channel labels, and displayed model name so the material goes to the intended partner.

The cards help you identify the channel and model to check. They do not show all network traffic or establish what a task actually transmitted. Resolve an Offline or Error state before submitting material.

3. Check the conversation and model setup

Open the agreed conversation from the partner card. Confirm the account, conversation or group, and who can see replies. Finish any pending channel setup or confirmation first. If several channels are connected, identify the one you will actually use for this task.

To check the model, open that partner's Model Configuration and review the current selection. Ask the person responsible for setup if the configuration or permission to use that service is unclear. Recheck the permitted input after a model change. Using your own account does not establish that every requirement has been met.

4. Submit a reduced working copy first

Copy only the passages needed for the task. Ask the partner to extract follow-up items from this input, flag missing owners or dates for confirmation, and return the result to the current conversation for review.

Task instructions communicate your intent but do not replace channel permissions or access restrictions. Check the relevant setup when sending messages or changing official files requires human approval. Leave unconfirmed actions out of the task.

5. Review the result and record the scope

When the reply arrives, confirm that it appeared in the agreed location, reached the intended audience, and contains no material outside the input you supplied. Compare it with the source for omissions and unresolved items.

Record the partner, conversation location, model name, input scope, and review date for the next check. Stop adding material if you find an unexpected recipient, unrelated information, or an unexplained action. Keep the relevant message and contact the maintainer, hiding private details before sharing a support screenshot.

Done when

The correct partner has processed one small, permitted input, you have reviewed the result in the agreed location, and the scope is recorded. Then extend the workflow to similar work. Repeat the check after a change to the partner, destination, or model.

Troubleshooting

• Working only from a desktop computer Still check the channel, model, and input. A local interface does not establish fully offline execution.
• A normal reply arrives This helps verify the result, but does not prove that no data left the device. Ask the maintainer to examine the relevant evidence when actual network behavior must be established.
• The client requires no data to leave the network Pause work with the real material and ask the deployment owner to verify the environment and services. A partner card or this checklist cannot establish isolation.

Related pages

Use the documentation navigation to open Connect and Manage Channels for an AI Partner for channel setup, Check AI Partner Status and Choose the Next Step for runtime issues, or Hand Over an AI Partner Task the Client Can Repeat for client delivery.

What changed

Replaced the general boundary overview with checks before submitting material, including reduced input, destination checks, and acceptance criteria. Removed broad promises about three levels of isolation.