Provider access is included. Tools that work in your own apps ask you to connect that account.

Every catalog item is a tool. Its access state tells you whether anything else is needed:

- **Ready to run** means Scrollport supplies provider access. The human or agent does not need to create another provider account, obtain an API key or buy a provider subscription.
- **Requires connected account** means the tool acts inside an external account the human already owns, such as a workspace, CRM or publishing account.

A connected account is authorised only when a selected tool needs it. The agent never asks for the provider password, API key or OAuth token in chat. Connecting an agent to Scrollport does not silently connect an external account, and authorising one external account does not grant access to another.

## The connection sequence

1. If the workflow already names an external account, call `list_apps` to check whether it is available and connected.
2. `search_tools` reports whether a candidate is ready to run or requires a connected account.
3. `inspect_tool` confirms the requirement for the selected `tool_id`.
4. If the app is disconnected, give its `connect_url` to the human and wait while they review and authorise the provider grant. A run can return the same `connection_required` handoff.
5. After the human finishes, call `list_apps` again to confirm readiness, then inspect the same `tool_id` before running it.

The resulting connection belongs to your Scrollport workspace and can be used by its authorised agents. Provider credentials never enter the agent's prompt.

## Control stays with the human

The provider's authorisation screen shows the account and permissions being requested. The human can decline the request, disconnect the provider later or revoke access at the provider. `list_apps` never starts that flow or exposes the provider identity behind it. Agents must never interpret a `connect_url` as permission to collect credentials or approve on the human's behalf.

A connected account is an authorisation mechanism, not a pricing promise. Use `inspect_tool` for the selected tool's current price, access state and worked example before every run. Scrollport charges only for successful requests; any separate provider charges remain governed by the account the human connected.

## Disconnecting and deleting connected data

The workspace owner or admin can disconnect an app at [Settings → Apps](https://scrollport.com/settings/apps). Disconnecting revokes the provider grant and prevents future calls; it does not rewrite an already-completed usage record.

Google Workspace raw run inputs, results and provider error content are retained for no more than 30 days. Private Google artifacts are retained for no more than 7 days, after which their links stop working and their bytes are deleted. Scrollport retains only non-content execution, authority, security and financial audit metadata where needed.

Email [privacy@scrollport.com](mailto:privacy@scrollport.com) to request access, export, correction, account closure or deletion. Final workspace closure immediately redacts eligible Google run content and expires its artifacts for physical deletion. See the [Privacy Policy](https://scrollport.com/privacy) for the complete scope and exceptions.

## If a connection fails

An unconnected run returns an error explaining which connection is required and where the human should go. A missing provider permission can still cause a provider-specific error after connection; read the returned `hint` and common errors instead of retrying the same input blindly.

## Check current availability

Connection status, provider availability, tool schema and pricing can change. This page explains the stable flow only. Browse the [live catalog](https://scrollport.com/tools) and call `inspect_tool` for the current selected tool.