Authorising a tool

A Connection is access you have authorised. You make one once, and from then on every Playbook that declares that tool finds it.

Where you do it

Two doors to the same place.

• Your account settings, under Connected Tools. This is the full directory: what you have connected, what is available, searchable and by category.
• From a Playbook. The same directory opens from the Playbook's resources, and a setup checklist item for a missing tool carries the control that connects it, so you fix it where you found it.

What happens when you connect

You are sent to the tool's own sign-in screen and grant access there. Nothing about that step happens on a YAMO form, and that is the point: your password never touches this platform.

What comes back and is stored is a reference to the authorised connection rather than the provider's credential. Revoking access at the provider ends it, and disconnecting here stops it resolving for every Playbook that relied on it.

The question you are asked

Every connection asks one thing before it is made: whose account is this? Yours, or a client's.

It is recorded once and it does not change, because "whose data was this" is a question that has to be answerable later rather than reconstructed. It matters most when a working relationship ends and there is a decision to make about what happens to the access.

Keeping one healthy

Access expires and gets revoked at the far end, and when it does the connection is reported as needing reconnection rather than left to fail in the middle of a run. Reconnecting is the same flow as connecting: back to the provider, grant again, done.