> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lovable.dev/llms.txt
> Use this file to discover all available pages before exploring further.
# Connect your app to Gemini Enterprise
> Connect your app to Gemini Enterprise to search and summarize connected enterprise data, show grounded answers with citations, and build search or chat experiences on top of your existing Gemini Enterprise engine.
export const connector_0 = "Gemini Enterprise"
[Gemini Enterprise](https://cloud.google.com/enterprise-search) is Google Cloud's search and grounded-answer platform for enterprise data. The Gemini Enterprise connector lets your Lovable app use the Gemini Enterprise engine you already configured in Google Cloud, so you can build search pages, Q\&A assistants, and internal tools on top of connected company data.
With Gemini Enterprise, your app can:
* Search connected data stores using natural language queries
* Return grounded answers with citations from your indexed content
* Support follow-up questions with multi-turn conversations
* Build search-first interfaces with ranked results, filters, and facets
* Inspect which data stores are connected to your Gemini Enterprise setup
What your app can do depends on the Gemini Enterprise engine you connect, the data stores attached to it, and the Google account used to authorize the connection.
## Why and when to use it
Use Gemini Enterprise when your organization already uses Gemini Enterprise or Vertex AI Search as the layer that unifies internal data sources. This connector is a good fit when you want Lovable to build on top of that existing search layer instead of calling each source system directly.
Gemini Enterprise works best for search and answer experiences such as internal knowledge search, support assistants, and research tools. It is not the right choice when you need direct write access to the source systems themselves, such as sending email, creating Jira issues, or modifying files in external tools.
## Common use cases and example apps
| Example app | Example prompt | Description |
| :---------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Internal knowledge assistant** | *Build a chat interface that answers employee questions using our Gemini Enterprise engine and always shows citations.* | **Create a grounded Q\&A experience on top of your indexed company content.**
The app asks Gemini Enterprise for grounded answers and displays source-backed responses with follow-up questions. |
| **Enterprise search portal** | *Build a search page for our Gemini Enterprise engine with filters, result cards, and a document preview panel.* | **Turn Gemini Enterprise into a structured search UI.**
The app returns ranked search results from connected data stores and lets users browse sources directly. |
| **Support knowledge tool** | *Build a support workspace where agents can search our help content and get a cited answer before replying to customers.* | **Help teams find trusted answers faster.**
The app combines search and grounded answer generation so agents can verify what the source documents actually say. |
| **Cross-source research assistant** | *Build a research assistant that searches across the data stores connected to our Gemini Enterprise app and summarizes the findings with citations.* | **Search across blended enterprise sources from one interface.**
The app uses your existing Gemini Enterprise setup to retrieve and summarize results across multiple connected data stores. |
| **Source explorer** | *Build an admin page that shows which data stores are connected to our Gemini Enterprise engine and lets users search within specific sources.* | **Make the search configuration visible inside your app.**
The app can list connected data stores, show their types, and target search experiences to selected sources. |
## Requirements and billing
Workspace **admins** and **owners** can create Gemini Enterprise connections.
Before connecting Gemini Enterprise, make sure you have:
* A Google Cloud project with a Gemini Enterprise or Vertex AI Search engine
* Data stores already connected to that engine in Google Cloud
* A Google account that can access the Gemini Enterprise engine and the connected content you want the app to use
* Your **GCP project ID**
* Your **Engine ID**
* Your **Location** (`global`, `us`, or `eu`)
* Lovable workspace admin or owner role
Gemini Enterprise usage, quotas, and billing are managed by Google Cloud. Requests made through this connector count toward your Google Cloud project, not Lovable.
### How Gemini Enterprise connections work
* Each connection stores the **GCP project ID**, **Location**, and **Engine ID** for one Gemini Enterprise engine.
* You authorize the connection with a Google account, and Lovable stores that access securely in the connector gateway with automatic refresh.
* Your app can use the connection across linked projects in the workspace.
* You can create multiple Gemini Enterprise connections if you need different engines, environments, or Google accounts.
* For Google Workspace and supported third-party sources connected through Gemini Enterprise, retrieval respects the access of the Google account used for the connection.
* Search results and grounded answers depend on both your Gemini Enterprise engine configuration and the access of the Google account used for the connection.
Gemini Enterprise can search data from Google and third-party sources that your Google Cloud admin has already connected to the engine. See Google's list of [supported data sources and connectors](https://docs.cloud.google.com/gemini/enterprise/docs/connectors/introduction-to-connectors-and-data-stores).
## Setup and configuration
Go to **Connectors → App connectors** and select **Gemini Enterprise**.
Click **Add connection**.
Enter a **Display name** such as `Gemini Enterprise Prod` or `Internal Search`.
Fill in the connection fields:
* **GCP project ID**: the Google Cloud project where your Gemini Enterprise engine lives
* **Location**: `global`, `us`, or `eu`
* **Engine ID**: the Gemini Enterprise engine identifier
If you open **Advanced settings**, you can review the Google permissions requested for the connection. The default selection is appropriate for most Gemini Enterprise setups.
Click **Connect**, sign in with Google, and approve the requested access. Lovable verifies that the project, location, engine, and account access are valid before creating the connection.
When connected, your Lovable apps can build both search-first and answer-first experiences on top of the same Gemini Enterprise engine.
### What to ask Lovable after connecting
Use prompts that make the intended experience clear. Gemini Enterprise supports both classic search interfaces and grounded chat-style answers.
```text wrap theme={null}
Build a search page for our Gemini Enterprise connection with a search bar, result cards, filters, and a detail panel for the selected document.
```
```text wrap theme={null}
Build a grounded Q&A assistant on top of our Gemini Enterprise connection. Show citations for every answer and support follow-up questions in the same conversation.
```
## Limitations and troubleshooting
* Each connection is tied to the Google account that authorized it. What your app can retrieve depends on that account's access.
* This connector supports Gemini Enterprise search and grounded answers. It does not expose raw APIs for systems behind Gemini Enterprise, such as Jira REST or Microsoft Graph.
* Gemini Enterprise actions that are only available in the Google Cloud console are not available through this connector.
* Website data stores are not supported for Gemini Enterprise search and assistant apps.
* If you see a **403** error, confirm the Google account can access the engine and the relevant data sources.
* If you see a **404** error, confirm the **GCP project ID**, **Location**, and **Engine ID** exactly match the engine in Google Cloud.
* If you see a **429** error, review quotas and rate limits in your Google Cloud project.
## How to unlink projects from a {connector_0} connection
Editors and above can remove specific projects from a connection without deleting the connection entirely. The connection will remain available for other projects.
To unlink projects:
Open **Connectors**, then go to **App connectors**, and select **{connector_0}**.
Open the connection you want to manage.
Under **Linked projects**, check the projects you want to unlink.
Click **Unlink projects** and confirm.
When unlinked, those projects will no longer have access to {connector_0} through this connection. If a project needs {connector_0} again, you can link it to any available connection.
## How to delete a {connector_0} connection
Workspace admins and owners can delete {connector_0} connections.
Deleting a connection is permanent and cannot be undone. It will remove the credentials from all linked projects, and any apps using this connection will stop working until a new connection is added.
Before deleting, review the **Linked projects** section to see which projects are currently using the connection.
To delete a connection:
Open **Connectors**, then go to **App connectors**, and select **{connector_0}**.
Open the connection you want to remove.
Review the **Linked projects** section.
Under **Delete this connection**, click **Delete** and confirm.