> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/keeperpam/secrets-manager/integrations/google-chat-app/publishing-the-keeper-google-chat-app-internally.md).

# Publishing the Keeper Google Chat App Internally

The Keeper Google Chat app must be published internally before it can be used by users in the organization. Once published, organization users can install the app and use it to raise access requests.

Official docs: [How to publish](https://developers.google.com/workspace/marketplace/how-to-publish)

### Phase 1 - Enable Marketplace SDK

1. Open [Google Cloud Console](https://console.cloud.google.com).
2. Select the Cloud project that owns your Chat app.
3. Go to **APIs & Services** -> **Library**.
4. Search for **Google Workspace Marketplace SDK**.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FX3anEOmbs0O1AbhflKR9%2Fpublish%20screen%201.png?alt=media&amp;token=9767330c-61a2-424a-9d0e-f527423a977a" alt=""><figcaption></figcaption></figure>

5. Open it and click **Enable**.

***

### Phase 2 - App Configuration

1. Go to **APIs & Services** -> **Google Workspace Marketplace SDK** -> **App Configuration**\
   (or search “Marketplace SDK” -> **Manage** -> **App Configuration**).
2. **App visibility** (critical -- cannot change later)
   * Select **Private**.
   * Only users in **your organization** can find/install the app.
   * Leave **Unlisted** off unless you want URL - only access (no Internal Apps browse/search).
3. **Installation Settings**
   * Select **Individual + Admin Install.**
4. **App integrations**
   * Check **Google Chat app** only.
5. **Developer information**
   * **Developer Name:** Enter your organization's name.
   * **Developer Website:** Enter your organization's website.
   * **Developer Email:** Enter the email address of the administrator or contact responsible for managing the app.
6. Click **Save** / **Save Draft**.

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FpbefSJ5omQdGqTZJX4sQ%2Fpublishing%20screen%202.png?alt=media&amp;token=f953ea85-5b44-4e4a-be03-c54358bfdd03" alt=""><figcaption></figcaption></figure>

{% hint style="danger" %}
If you see the message **“The OAuth consent screen must be enabled for this project”**, complete the following steps:

1. Click **Get Started**.
2. Enter **Keeper Security** as the **App name**.
3. Enter your company's **support email address** -> Click **Next**.
4. Under **Audience**, select **Internal** -> Click **Next**.
5. Enter your **contact information**.
   {% endhint %}

***

### Phase 3 — Store Listing

1. Go to **APIs & Services** -> **Google Workspace Marketplace SDK** -> **Store Listing**.
2. **App details**

   * Language (default + any translations).
   * Application name (align with Chat display name).
   * Short description: `Keeper vault credentials access in chat`
   * Detailed description:&#x20;

   **`Keeper Security is a zero-trust, zero-knowledge cybersecurity platform`**` ``that provides password management, secrets management, and privileged access control.`&#x20;

* Category: Free of price
* Category: Web Development

1. **Graphic assets**
   * Upload icons (**32×32**, **128×128**).

{% file src="/files/jLEiLhyFQCqLdzf6ogkl" %}

{% file src="/files/f3phHhs3ldhCTWsxLfZK" %}

* Upload card banner (**220×140**).

{% file src="/files/TRNj13KmEXAbJZpoTgbW" %}

* Upload at least one screenshot of the Chat app in use.

{% file src="/files/yMtgONWoJkwWWRLunqR6" %}

1. **Support links** (required)
   * Terms of service URL: <https://www.keepersecurity.com/en_GB/legal/terms-of-use/?s=tou>
   * Privacy policy URL: <https://www.keepersecurity.com/en_GB/legal/terms-of-use/?s=privacy>
   * Support URL: <https://www.keepersecurity.com/en_GB/support.html>
2. **Distribution** (optional): leave all regions, or limit as needed.
3. Then Click on publish.

{% hint style="warning" %}
**Debug:** If you receive an error such as **“Please enter the detailed description again,”** simply refresh the page and enter the Description click the publish button again.
{% endhint %}

***

### Phase 4 — Verify

1. Once published, users within the organization can find and install the Keeper Chat app from Google Chat.
   * After installing the app, users can use the available slash commands to raise Keeper access requests.
   * Verify that the request is successfully received and the approval workflow is triggered.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.keeper.io/keeperpam/secrets-manager/integrations/google-chat-app/publishing-the-keeper-google-chat-app-internally.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.