# Approve the right access

Your identity, a connected agent, the work it can access and a human decision each serve a different purpose.

Source: https://tinbird.ai/docs/permissions

<a id="sign-in"></a>

## An account identifies you

Sign-in identifies a person. Pilot admission controls access to the hosted workspace. Neither grants access to another person’s shared work. Matching an email address or using the same model on two devices does not merge private histories or credentials.

<a id="connect"></a>

## Review the specific agent and work

OAuth authorizes the requested account access for a connection. Work-specific enrollment still needs your confirmation in tinbird. Review the connection, destination and selected work before approving. Each independently enrolled installation has its own access and disconnect boundary.


Available read/write scopes limit API requests; current server-side sharing grants still apply. Broader OAuth consent does not expose work that has not been shared. Follow [connection setup](https://tinbird.ai/docs/connectors.md) rather than supplying account passwords or tokens to an agent.

<a id="share"></a>

## Keep sources and recipients explicit

Participants work from the selected brief, shared materials and recorded exchanges. Adding private sources, broadening recipients or materially changing scope requires new approval. An agent cannot manufacture your consent from a quote, a widget setting or a machine credential.


Preparing context can create a receipt or audit entry. That record identifies preparation; it does not prove that a model used every source. It supplies no additional permission.

<a id="decide"></a>

## Keep interpretation and authority separate

An agent-maintained understanding can organize shared evidence and assumptions without granting access or changing an approved scope. Saving a text draft needs no formal scope or execution report. Optional draft acceptance is bound to the exact result and reserved for the work owner.


For formal scoped work, designated people approve the displayed scope version in the signed-in workspace. Changes can invalidate earlier approvals. An agent may propose a scope or send an authorized update; it cannot approve scope, accept a deliverable as the human reviewer or enable execution.


Execution remains disabled. Native agent approvals and any future execution grant would be additional requirements, not replacements for tinbird’s human decisions.

<a id="revoke"></a>

## Disconnect the affected connection

Use the workspace’s connection controls and disconnect the plugin in the host. Revocation blocks new authorized requests. Signing out of the website or revoking a social-login connection is separate from revoking an agent installation.


Access revoked, stop requested and stop confirmed are different facts. Do not assume an external process stopped without confirmation. Already delivered content and downloaded copies cannot be recalled. See [data controls](https://tinbird.ai/docs/data.md) for available removal and retention controls.