> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gol.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Connections and owner approvals

> Review connected AI apps, inspect their access, and approve requests in the correct account.

Connections shows AI apps that have access to your GOL account. Product connections and paired-agent mandates have different permissions and network requirements. Check the account, network, and exact access shown in each request.

![The current Connections page and its preview explanation for connected AI apps](https://mintcdn.com/gol-docs/zEEOA3Rc-vjx7smD/images/app/framed/connections.png?fit=max\&auto=format\&n=zEEOA3Rc-vjx7smD\&q=85\&s=a15fa1e3b24a7d6b3a5568e6ecd288a2)

The Connections UI in mock mode. This preview does not fetch live connected apps or approve a real request.

## Connect an AI app

Start from the GOL connector setup in your AI app. When it opens GOL's consent page, sign in and review the app identity, return destination, selected account, and requested permissions. Approve only the access you intend to give, or deny the request. Availability and account requirements differ by client. Client and device testing is incomplete.

Connecting an AI app does not hand it your private keys. Permission to read data, manage agent records, or prepare a wallet action is different from permission to execute a transfer.

## Understand access

| Access | What it permits |
| - | - |
| Read wallet, Vault, or agent data | See the account information included in the approved scope. |
| Request a wallet or Vault action | Prepare an action for your review and signature. The request itself moves no funds. |
| Manage agents or marketplace listings | Perform the approved record-management actions. New agents start in paper mode. |
| Control trading or Vault automation | Use the supported controls within permissions already granted. It does not create a new wallet grant by itself. |
| Request a mandate | Ask you to approve bounded authority through the separate mandate flow. Paired-agent mandate controls require their stated Base Sepolia account. |

## Review an owner request

Open the request from the originating AI app or its pending-request link. Check that the displayed owner and network match the wallet you intend to use. If the account is wrong, switch or link the correct account rather than approving with another wallet.

Read the action details, amounts, recipients, limits, expiry, and warnings that apply. A product action uses its normal review and wallet-signing controls. A mandate request authorizes bounded future actions; inspect its full terms before signing. Requests can expire or be refused by service, account, or simulation checks.

A proposal, an accepted request, and a confirmed transaction are different states. If an outcome is uncertain, reopen the same request or inspect the known transaction. Do not create another value-moving action just because a response was lost.

## Disconnect and remove authority

Open **Connections**, inspect the app's permissions and account, then select **Disconnect**. The page also identifies connections that need reconnecting and retains disconnected entries where available.

> [!WARNING]
>
> Disconnecting removes that AI app's GOL access. It does not remove a wallet
> signer, revoke an on-chain mandate, sell positions, or stop a separately
> scheduled agent. Use each feature's own controls to remove those permissions
> too.

If paired-agent controls say **Coming soon** or require a verified account, do not substitute a Mainnet wallet for the specified testnet account. Product AI app connections can remain available independently of those older pairing controls. See [security and control](https://docs.gol.network/app/safety.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.