> For the complete documentation index, see [llms.txt](https://docs.opsmx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsmx.com/integrations/integrating-ci-and-cd-tools/helm.md).

# Helm

Helm is a tool that streamlines kubernetes deployments and management with Helm's pre-configured charts and automated upgrades. 

### Usage of Helm in Delivery Shield

* Delivery Shield integrates with Helm to bring visibility into Kubernetes deployment manifests and chart configurations used during releases.
* Chart-level details are evaluated against secure software delivery policies and factored into the application's overall security score.

### To Integrate Helm:

1. Navigate to **Setup** > **Integrations**.
2. In the **Source** panel, click **Helm**.
3. The Helm integration page is displayed. Click **+New Account**.

<figure><img src="/files/AXYReGUZ2ncYsJN84w9B" alt=""><figcaption></figcaption></figure>

4. In the popup that appears, enter the following details:

<figure><img src="/files/UG2wkbd4vtr9m84pi8U6" alt=""><figcaption></figcaption></figure>

5. Enter the **Account Name, Repository Name, Repository URL**.
6. Select the **Teams** and the corresponding **Environments** from the dropdown for which you want the integration to be available. The integration will be available for the selected teams and environment only.&#x20;

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>You can select up to 5 teams for the integration to be displayed. </p></div>

   * An example is given below for reference:

   <figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeuMZQzZsZQuulVdW9B9OuffNPoEXqbcpcAkYtKVyb7YiTQxbVIt1L4Gh-zshqX2J9MFKIat8x4oWFIGxdg3j1XVagyUNhUAlD_52soyMyd1cy53p6XiYi0LsTjIBfHcybRWl61?key=D9EXoOdGF7oYOBvYaW2GnRWJ" alt=""><figcaption></figcaption></figure>

   * In the example above,&#x20;
     * if **Team 1**, **Team 2**, and **Team 3** are selected, only applications associated with these teams can access the integration. Any applications belonging to other teams, such as **Team 4**, will not have access to this account.
     * Even if the user who created this account is also an admin for **Team 4**, the integration account remains restricted and is not available for **Team 4**.&#x20;
     * Access to the account is strictly limited to the specified **Teams** and **Environments** selected during account creation.
   * **For Organization Admins:**
     * When an **Organization Admin** creates an account without selecting specific **Teams** and **Environments**, the account will be universally applicable, granting access to **all teams** and **all environments** by default.
   * **For Team Admins with Multiple Teams:**<br>
     * If a **Team Admin** who manages multiple teams creates an account without specifying particular **Teams** and **Environments**, the account will only be accessible to the teams for which the logged-in user holds admin privileges.
7. Enable **Private Mode** if needed.&#x20;
8. Click **Save**. The tool is integrated in the source stage.&#x20;
9. You can edit the entered Gitlab values by clicking the **Edit** option as shown below:

<figure><img src="/files/h7rXWjKSO5NeuDwGVZGA" alt=""><figcaption></figcaption></figure>

8. Enter the new values and click **Update**.&#x20;

<figure><img src="/files/IP9kh7PqHDxdIfN03fnw" alt=""><figcaption></figcaption></figure>

The new values get updated.&#x20;

\
\ <br>