> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/application-security/software-supply-chain-security/visibililty-and-inventory/supply-chain-assets/vcs-collaborators-as-assets.md). # VCS collaborators as assets The **VCS Collaborator** (collaborators) asset inventory provides a centralized view of all collaborators (users) who interact with VCS repositories, CI/CD pipelines, and related assets. The platform enables efficient discovery and management of these assets, providing insights and analysis to contextualize their importance within your ecosystem and assess their risk posture. You can directly access related issues and findings within the collaborator asset inventory, allowing you to prioritize and remediate them without navigating to a separate remediation section. ## How to access collaborator assets * To access Collaborator assets, under **Identity**, select **Human Identities** → **select VCS Collaborator from the Type filter**. ## Investigate Collaborator asset information Click an asset in the inventory table to open its side card, providing in-depth information organized into several tabs. {% tabs %} {% tab title="Overview" %} The Collaborator asset summary, displayed at the top of the card, provides concise details about the collaborator, such as their name and the version control system that the collaborator is associated with. The **Overview** tab summarizes the collaborator highlights and properties. **Highlights** include: * **Critical/High issues**: An aggregation of critical and high issues associated with the collaborator * **New**: Whether the collaborator was recently added to the VCS organization * **Inactive**: Indicates whether the collaborator has had no commits within the last time period **Properties** include: * **Risk Summary**: The amount of risks associated with the collaborator grouped by category (cases, issues and findings) and their severity level * Asset details, including **Asset Id**, **Asset Types** and **Asset Groups** associated with the collaborator * **Visibility timeline**: When the collaborator was first and last detected * **Identity and Affiliation**: * **Username**: the alias associated with the collaborator * **User Type**: The classification of the collaborator's account (such as individual user, service account, bot), indicating the nature of their access and activity * **VCS Organization**: The specific version control system organization to which the collaborator belongs or has access * **Emails**: "The email addresses associated with the collaborator's account, used for communication and notifications * **Access and Activity**: * **Team Membership**: The teams or groups within the VCS Organization to which the collaborator belongs, defining their access permissions and collaborative roles * **Last Commit**: The timestamp of the collaborator's most recent commit to a repository within the associated VCS Organization, indicating their recent activity The **Highlights** section and other asset properties only display attributes when their corresponding indicators are present. For example, if an asset is not deployed, its deployment-related attributes will not show up; similarly, if there are no detected issues, those highlights or properties will not appear. {% endtab %} {% tab title="Access" %} The **Access** tab provides a list of assets that a VCS Collaborator has access to within your environment. It details the specific assets they can interact with, the level of permission granted, and the timestamp of their most recent code commit to that asset. {% endtab %} {% endtabs %} ## Manage Collaborator assets You can perform the following actions collaborator assets. **Asset actions** * Right-click on an asset in an inventory table to access the **Actions** menu, where you can perform the following actions: * **Open in new tab**: Opens the description tab of the asset for detailed analysis of the issue * **View asset data**: Opens a new pop-up window displaying the data retrieved for the asset during the most recent scan in either JSON (default) or tree view. This raw data provides a comprehensive and unformatted view of the asset's properties and attributes as they were initially ingested * **Copy text to clipboard**: Copies the selected text to the clipboard * **Copy entire row**: Copies the entire selected row data * **Show/hide rows**: Stand on data in a row and filter the entire inventory to show or hide assets based on the selected attribute * **Open in Cortex Assistant/Open in Cortex Agentic Assistant**: Opens the repository in Cortex Assistant or Cortex Agentic Assistant. * **Export asset data**: Click the download icon (showing **Export to file** when hovering over the icon) in the top right of any asset page to export the asset data * **View Dashboard**: Redirects to the [Application Security](/application-security/application-security/cortex-cloud-application-security-dashboard.md) dashboard --- # 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://cortex-docs.paloaltonetworks.com/application-security/software-supply-chain-security/visibililty-and-inventory/supply-chain-assets/vcs-collaborators-as-assets.md?ask=&goal= ``` `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.