Skip to main content

Gemini Enterprise

Reach your Gemini Enterprise apps, agents and data stores on Google Cloud from agent sessions.

Connect it with: Service account. Gemini Enterprise's own documentation: https://docs.cloud.google.com/gemini/enterprise/docs/authentication.

What agents can do​

Connect Gemini Enterprise so the agents working your tasks can reach it. With it connected, they can:

  • List the Gemini Enterprise apps (engines), data stores and agents in your project.
  • Search and ask questions across the data your Gemini Enterprise apps index, with answers grounded in your company data.
  • Read and update data store documents when the service account's role allows it.

Before you start​

  • A Google Cloud project with Gemini Enterprise set up and the Discovery Engine API enabled.
  • Permission to create service accounts and keys in that project (Service Account Admin and Service Account Key Admin), or an admin who can do it for you.
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with Gemini Enterprise​

Jaah connects to Gemini Enterprise with a service account, not with a sign-in button.

Connect with an API key​

Find each value first:

  • Service account key: In the Google Cloud console open IAM & Admin > Service Accounts in the project that holds Gemini Enterprise, create or pick a service account, grant it the Discovery Engine Viewer role (more if agents should change things), then open its Keys tab > Add key > Create new key > JSON and paste the whole downloaded file.
  • Project ID (optional): The Google Cloud project id shown in the console's project picker; leave blank to use the key's own project.
  • Location (optional): Where your Gemini Enterprise apps live, as shown on the Gemini Enterprise > Apps page in the console: global, us or eu.

Then add it to Jaah:

  1. In Jaah, open Secrets, select New, and pick the Gemini Enterprise card.
  2. Name the secret and choose who can use it.
  3. Fill in Service account key, Project ID, Location.
  4. Select Save. Jaah tests the secret straight away (see Test the connection).

Jaah encrypts what you type and never shows it again — not to you, and not to an admin.

Use your own OAuth app​

Not used: Jaah connects to Gemini Enterprise with a service account, not through an OAuth app.

Test the connection​

Select Test on the secret. Jaah makes one read-only call to Gemini Enterprise with the stored values and shows the result on the secret's page. Jaah also tests automatically when you save or reconnect.

Who can use it​

Every secret has an owner, and the owner decides who can use it:

  • Personal — only your own tasks can use it. This is the default.
  • Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
  • Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.

More on owners and access: How secrets work.

Use it in an agent session​

An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:

  • org/<name> for an organization secret,
  • projects/<project>/<name> for one attached to a project,
  • me/<name> for your personal one.

A key connection hands the agent its fields: service_account_json, project_id, location.

Tell the agent in your task description which secret to use, for example “use the Gemini Enterprise secret org/gemini-enterprise”.

Manage, rotate or disconnect​

Everything is on the secret's page under Secrets:

  • Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Gemini Enterprise once the test passes. Steps: Replace or delete a secret.
  • Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Gemini Enterprise's side too, delete the service account's key in its cloud console.

Limitations​

  • Jaah connects with a service account key only; sign-in as a person and Workload Identity Federation are not offered yet.
  • The Test checks the default collection of one location only (global, us or eu).
  • Agents act with the service account's IAM roles, not as an end user, so per-user document permissions in your data stores do not apply.
  • Agents can do only what the connected Gemini Enterprise service account and its roles allow.

Troubleshooting​

The Test says Gemini Enterprise rejected the service account key (403) and Google names a missing permission

Grant the service account the Discovery Engine Viewer role (roles/discoveryengine.viewer) in IAM & Admin > IAM, and check that the Discovery Engine API is enabled in APIs & Services.

The Test says Google refused: Invalid JWT Signature

The key was deleted or the file was changed. Create a new JSON key on the service account's Keys tab and select Replace.

The Test passes but reports 0 apps

The apps live in another location or project. Set Location to us or eu, or set Project ID to the project shown on the Gemini Enterprise > Apps page.

Still stuck? Select Test and read the result: it names the value Gemini Enterprise refused and the status it answered.

FAQ​

Is this the same as a Gemini API key?

No. A Gemini API key from Google AI Studio calls the Gemini models; Gemini Enterprise is the Google Cloud product for company search and agents, reached with Google Cloud credentials.

Does Jaah keep the private key?

It stores the key file encrypted and uses it only to mint short-lived Google access tokens; the key itself is never sent anywhere but to the agent that is allowed to use it.

Can Jaah or an admin see the key or token?

No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.

Can I connect more than one Gemini Enterprise account?

Yes. Add one secret per account, each with its own name, and tell the agent which one to use.