# Connector acceptance: is a connection pilot-ready?

Decide whether a connection is ready for your pilot. An integration name does not establish that a particular workflow works. Evaluate a connection against the exact information, permissions, and output your pilot needs.

Updated October 15, 2026

## Define the smallest required operation

Describe the operation in ordinary language: retrieve the approved onboarding handbook from one agreed folder, for example. Identify the source account, the expected version, and the person who owns access. Keep reading separate from changing or publishing information. A successful read is not evidence that a write operation is available or permitted.

## Confirm availability with the delivery owner

Ask which connector and environment will be used, what authentication method applies, and which limitations affect the task. Record the answer and date. Google Drive and Notion connect to Company Knowledge directly and other company tools are connected with our team; this educational page does not confirm a connector for your environment. Resolve availability before making the pilot dependent on it.

## Check the result against the source

Use approved test material with an easily recognized title and version. Retrieve it through the intended workflow and compare the returned content with the original. Verify that the right account was used. Ask a reviewer to inspect a deliberately changed source so that freshness can be evaluated rather than assumed.

## Check the boundaries of access

Include an item outside the permitted folder and a user without the required role. The expected result is a clear denial or absence of that content, not an improvised answer. Test expired access and disconnection with the delivery owner. Record what happens to existing imported material; do not assume revocation automatically deletes it.

## Choose a fallback before launch

If the connection cannot pass the agreed checks, reduce the pilot's scope or use a permitted manual source pack with a documented update owner. Label that workflow accurately. Acceptance requires evidence for the actual route used, plus an understandable recovery path, rather than a logo or a successful authentication screen.