Connections
A connection lets Optiak access an external tool server, data source, or supported model subscription. Organization Admins create organization connections; applications use the tools, data, or models the organization makes available.
Required role
Applies to
Why use it
Keep third-party sign-in and credentials in Optiak instead of copying them into each application. A connection centralizes which identity is used and what it can access.
How it works
An Organization Admin creates a connection while setting up a tool server, a data source, or authorizes a supported model subscription. The authorization method depends on the service: it can use OAuth, a device code, an API key or token, service-account credentials, or no authentication when the server allows it.
Tool and Data Integration setups share their connection with every application assigned to them. A model subscription connection is organization-wide; the organization enables its supported models for applications. Disconnecting a shared connection can interrupt every application that uses the setup or model.
Connect and manage connections
Connect subscriptions
Connect a subscription when your organization wants to use models included with a provider account. For example, an Organization Admin can authorize a ChatGPT subscription to make Codex models available. The connection is organization-wide rather than assigned to individual applications.
In Company setup → Providers, open Codex and connect the ChatGPT account. After authorization, review the available models in Company setup → Models and enable the ones applications should use. Only enabled models are available to applications. See Models and Routing for using enabled models in requests.
Connect tools
Use a connection when an MCP server requires an identity or credential. Some servers use OAuth, some use an API key or token, and public or network-restricted servers may need no authentication. The server determines which methods it supports.
In Company setup → Tools, connect the server, discover its tools, choose which ones to expose, and assign the setup to applications. See Tools for how applications use enabled tools.
Connect data sources
Data sources can use a connection to access the external account that holds their documents. The applications using the related Data Integration share that connected identity; they do not sign in separately to the source.
In Company setup → Data integrations, connect the source and choose which applications can use it. Applications then enable the available Data Integrations in Configuration. See Data Integrations for how retrieval works.
Set it up
- Connect MCP Servers: connect external tool servers and choose their authentication method.
- Connect Data Sources: connect Google Drive and Notion accounts used by Data Integrations.
Limits and behavior
- Authentication options vary by service. Use only methods supported by the provider or server.
- Disconnecting a connection detaches and deactivates every linked tool server or Data Integration, so assigned applications lose access. Reconnect the service or provide its credentials again, then reactivate each affected setup before applications can use it again.
- Before changing or disconnecting a connection, check its assignments; the change can affect every application using those setups.
Related
- Authentication: Application API keys and provider credentials.
- Tools: choose and use tools in an application.
- Data Integrations: add connected document sources to requests.