# Custom Policy Source

Custom policy source refers to a mechanism or source from which CI systems can retrieve and apply custom policies or rules to the code being built or integrated. These policies or rules could be related to coding standards, security checks, compliance requirements, or any other guidelines that the development team wants to enforce as part of the process.

### Usage of Custom Policy Source in Delivery Shield

* Users can import existing security policies from their organization or create new policies using the custom policy source. 
* Delivery Shield will periodically scan the custom policy repository to detect and import any changes. For more information, see [Custom Policies](https://docs.opsmx.com/opsmx-secure-software-delivery-ssd-platform/user-guide/manage-policies/global-policies#sync-policies).

### To Manage Custom Policy Source:

1. Navigate to **Setup** > **Integrations**.
2. In the **Others** panel, click **Custom Policy Source**.

<figure><img src="https://2047464521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MBEa1hoX6SqpDj-ymNs%2Fuploads%2F98rQlwAjaztnHQHpX3iz%2Fcustom%20policy%201.png?alt=media&#x26;token=5de54c5e-ae23-4060-8cbe-1a4e61ecfaf8" alt=""><figcaption></figcaption></figure>

3. The Custom Policy Source integration page is displayed. Click **+New Account**.
4. In the popup that appears, enter the following details:

<figure><img src="https://2047464521-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MBEa1hoX6SqpDj-ymNs%2Fuploads%2F5LN6sjSMnOZ397feEqvJ%2Fcustom%20policy%202.png?alt=media&#x26;token=c9905ccc-6eac-4744-bbad-8ddfdb1277e3" alt=""><figcaption></figcaption></figure>

5. Enter the **Account Name**, **Repo URL & Path** and **Token.**&#x20;
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>

   * A sample 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:**
     * 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. Click **Save**. The tool is connected.&#x20;
8. You can edit the entered values by clicking the **Edit** option in the Actions column.
9. Re-enter the values and click **Update**.&#x20;

The new values gets updated.&#x20;

<br>