> ## Documentation Index
> Fetch the complete documentation index at: https://plasma-ai.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Integration settings

> Manage connected accounts, workspace availability, and provider permissions.

Integration setup has three separate steps: authorize an account, make the connection available in a workspace, and give the agent the access it needs.

## Organization connections

Open **Integrations** and choose the provider. Supported providers show their connected accounts and available connection, reconnection, credential-update, or disconnect controls.

Use account labels to distinguish multiple connections to the same provider. Renaming a label does not change the underlying authorized account.

For ordinary organization connections, adding a connection does not automatically attach it to every workspace. Use each workspace's **Integrations** area to add it where needed.

## Workspace and agent access

A workspace attachment is a resource with its own access settings. An agent may read a public integration resource without joining it. Supported mutations also require the applicable membership, operation policy, and provider permissions.

Removing a workspace attachment is different from disconnecting the underlying organization connection. Disconnecting can affect every workspace using that connection.

## Google accounts

Direct Google connections are tied to the connecting user, workspace, service, and account. Connect or reconnect them from the workspace's **Integrations** page. They are not interchangeable organization-wide credentials.

Review the selected account and capability permissions. Multiple Google accounts can remain separate connections, and other organization members cannot manage someone else's personal Google authorization.

## GitHub installations

GitHub settings show **Connected installations** and account connection options. The provider's installation permissions determine which repositories are available.

Disconnecting revokes the organization's access through Fractal and makes dependent workspace repository resources unavailable until reconnection.

## Model-provider keys

Supported Anthropic and OpenAI BYOK keys are organization model-billing settings. They do not require a workspace integration attachment or resource membership.

BYOK eligibility, provider limits, and platform spending limits still apply. See [Credits, subscriptions, and BYOK](/fractal-product/billing/credits-and-byok).

## Read-only and write capabilities

An integration only exposes supported operations. A provider's broad authorization does not mean every provider feature is available through Fractal.

Read the provider's displayed permissions and [Capabilities and permissions](/fractal-product/integrations/capabilities). Agent operation policy and provider authorization both constrain a tool call.

See [Set up GitHub](/fractal-product/integrations/github) for the complete installation and workspace repository flow, including missing repositories and disconnection behavior.


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