> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/application-security/visibility/technologies/vcs-third-parties.md).

# VCS 3rd Parties

**VCS 3rd Parties** displays an inventory of third party applications (apps) and webhooks found in your organization’s version control system (VCS). This allows you to understand where they are in use in the organization, and to remove unused apps or webhooks in order to reduce your attack surface. In addition, you can view and understand permissions that applications have and remove excessive permissions where not required. This will help you abide by the 'least permission' principle, which states that applications should only be granted the permissions that they need to do their job.

To access ''VCS 3rd Parties', in **Application Security** select > **Home** > **Technologies** > click on the **VCS 3rd Parties** tab.

<figure><img src="/files/EJkX5Z3eFRKNwOrrjps2" alt="technologies vcs 3rdparty.3.1"><figcaption></figcaption></figure>

The **VCS 3rd Parties** inventory includes the following details:

* **Name**: The application/webhook name
* **Type**: The type of third party. Values: 'App', 'Webhook'
* **Scope**: The scope of the application/webhook. Values: 'Organization', 'Repository', 'Subscription', 'Team'
* **Permissions**: A summary of permissions granted to an application. See the 'Details' tab of the resource explorer for additional details about permissions when available
* **VCS**: The VCS hosting the application/webhook
* **Organization**: The organization in the VCS hosting the third party
* **Repos**: The number of repositories that host the application/webhook. See the **Repositories** tab of the resource explorer below for more details

Selecting an entity in the inventory table opens the **resource explorer** displaying additional information about the entity.

* The **Details** tab opens as the default view, providing third party metadata such as a list permissions that the app has been granted and a list of events that the app or webhook listens to

  <figure><img src="/files/oQlfZFtf7tpWrDqDYIPk" alt="technologies vcs3rdparties details3.1"><figcaption></figcaption></figure>
* The **Repositories** tab displays a list of repositories in your organization hosting the apps or webhooks. Includes a link to the repositories

  <figure><img src="/files/QkSvB3FC0lvZYWrjJNot" alt="technologies vcsthirdparties repositories3.1"><figcaption></figcaption></figure>
* The **URL** tab provides a list of the webhook URLs detected

  <figure><img src="/files/JE8VdHge907JW6c9dxBu" alt="technologies vcsvthirdparties url3.1"><figcaption></figcaption></figure>

## Filters

You can apply the following filters to narrow a search for a third party application or webhook.

* **Repository**: Filter by repositories in the system
* **Type**: Filter by application, webhook or both
* **Scope**: Filter by repository, organization or subscription
* **URL**: Filter by webhook URL
* **VCS**: Filter by the VCS in use in your organization. Values: 'GitHub', 'GitLab', 'Azure DevOps' and 'Bitbucket'


---

# 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.prismacloud.io/content-collections/application-security/visibility/technologies/vcs-third-parties.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.
