youroleriainstancename-governance.oleria.io, under AI Agent Gateway.
Oleria holds every credential you authorize here. Your agent never receives one - it asks the gateway, and the gateway makes the call.
Your administrator decides which applications appear here. If something you need is missing, ask an Oleria Administrator to enable it. See Administrator setup.
Connect your applications
Authorize each application once. Oleria stores the resulting credential and injects it per call - your agent never receives it.1
Open the OAuth Access tab
Go to AI Agent Gateway -> OAuth Access. Every application your administrator has enabled is listed, with its current status.

2
Connect an application
Select Connect next to the application. Oleria sends you to that provider’s sign-in and consent screen.
3
Authorize the connection
Sign in to the application as yourself and approve the access it requests. The consent screen names Oleria as the application asking for access, and lists exactly what it will be able to reach.
Approve it, and the provider returns you to Oleria with the application’s status changed to Connected.

4
Repeat for each application
Connect every application you want your agent to use. You can disconnect any of them later with Disconnect - the agent loses that access immediately.
You can only connect applications your administrator has enabled. If an application you need isn’t listed, ask an Oleria Administrator to enable it. If a connection is missing at runtime, the gateway tells the agent the application isn’t connected, so it can ask you to connect it instead of failing silently.
Next step
With your applications connected, add the gateway to your AI agent and start working. There are two ways it gets there, and both end with you signed in as yourself:- Your administrator published it. The gateway is already listed in your AI tool’s connectors, with an authorization of Individual, and you only need to sign in.
- You add it yourself. If it isn’t listed, you can add it as a custom connector using your gateway’s MCP endpoint. This needs no administrator access, and the connector you add behaves exactly like a published one.

