Find the insights and best practices about our product.
My Vendors Overview

Introduction

My Vendors is where you manage the vendors your organization works with and review the AI Cards they share with you. Add vendors directly, record your own information about each one with custom fields, keep a list of contacts at each vendor, and see the AI Cards you have received from external organizations in a single, searchable workspace. To access it, navigate to AI System Manager in the left navigation and select My Vendors.

My Vendors and its vendor detail pages require both the AISystem_Publish_Received_Read and Vendor_Vendor_Read_Tenant permissions. Links to My Vendors from the dashboard also require both permissions. A role with these permissions can also read vendor records and custom vendor fields. To keep vendor details from a role, remove Vendor_Vendor_Read_Tenant. That role then loses access to My Vendors.

Editing vendor contacts requires the Vendor Update permission, and importing vendors requires the Vendor Import permission. On tenants whose license includes vendor management, the tenant Admin role and the Standard User role hold both permissions by default. Other roles need them added.

Please note that only AI Cards received through the standard publish-and-received workflow appear in My Vendors. AI Cards uploaded directly to the platform are not included.

Summary Metrics

A KPI bar at the top of the page displays five metrics that reflect your current vendor compliance structure:

  • Total Vendors
  • Total AI Cards
  • Pending AI Cards
  • Declined AI Cards
  • Overdue AI Cards

Viewing Your Vendors & Received AI Cards

My Vendors offers two ways to browse your received data, controlled by a toggle at the top of the page: View By Vendor and View By Received AI Card.

View by Vendor

The View By Vendor view displays a searchable grid of vendor cards. It lists every vendor you track, including vendors you've added that haven't shared an AI Card yet. AI Card publishers that belong to the same vendor appear as one vendor card with combined counts. You can sort the grid alphabetically or by most recently updated. Each vendor card shows the vendor name, and counts for AI Cards, BOMs, Compliance Frameworks, and Documents associated with that vendor, along with a last-updated timestamp. Click View Details on any vendor card to open the vendor detail page.

Switch to the list view to see vendors in a table. Use Customize Table to show custom vendor fields as columns. Each user's column choices are saved separately, and custom columns can't be sorted.

View by Received AI Card

The View By Received AI Card view displays a grid of individual AI Cards received from your vendors. Each card shows the AI Card name, the associated AI System name, the date the card was sent, and an artifact breakdown with progress bars and counts for BOMs, Compliance Frameworks, and Documents. The date sent is when the vendor sent the card, or N/A when that time is not known. When the vendor shares vulnerability data, the card also shows a Vulns (N) panel. The panel gives the total number of shared vulnerabilities, with a model chart and a technology chart by severity. Click View Details on any card to open the AI Card detail view.

Add, Edit, and Retire Vendors

Add a vendor directly when your organization starts working with it, whether or not it has shared an AI Card. Select Add Vendor to open the Add Vendor form:

  • Name: The vendor's display name. Required.
  • Legal Name: The vendor's legal entity name.
  • Primary Domain: The vendor's main domain, such as example.com.
  • Website: The vendor's website URL.
  • Description: Free text about the vendor.
  • Custom Fields: A field for each of your organization's active custom vendor fields. Required custom fields must be filled in.

If the new vendor has the same domain or a similar name as existing vendors, a warning titled Similar vendors already exist lists up to five of them, each with a Go to vendor link. Use the links to check for a duplicate. The warning does not stop you saving.

To change a vendor's details, open its detail page and select Edit Vendor. The Edit Vendor form has the same fields as Add Vendor, filled in with the vendor's current values. AI Cards you have already received stay linked to the vendor when you rename it or when the publisher renames itself.

To retire a vendor your organization no longer works with, open its detail page and select Retire Vendor. A retired vendor and its AI Cards no longer appear in My Vendors or count toward the summary metrics, but they aren't deleted. You can't reactivate a retired vendor.

Retiring a vendor also hides its contacts from lookups and from the vendor and contact pickers on AI Card requests. Past requests and published AI Cards still show them. This applies to vendors retired before contacts were introduced as well.

Organizations that have sent you AI Cards but aren't set up as vendors still appear in My Vendors. You can't edit or retire them until you add them as vendors.

Adding, editing, and retiring vendors requires the vendor Create, Update, or Delete permission, respectively.

Importing Vendors

Import vendors when you need to add many at once, such as when you move an existing supplier list into My Vendors. Select Import Vendors on My Vendors to add vendors from a CSV file. Download template gives you a file with the expected layout. The Import Vendors button appears only to users with the Vendor Import permission.

For the file rules, how matching works and how to read the import results, see the Importing Vendors from a CSV File article.

Custom Vendor Fields

Custom vendor fields record the information your organization tracks for every vendor, such as a supplier number, risk tier, or contract owner. Anyone who can edit vendors can manage custom fields.

Select Manage Custom Fields to open the Custom Fields dialog. Select Add Field to add a field, then set its properties:

  • Label: The name shown on the vendor form and detail page.
  • Key: The field's identifier, suggested from the label. The key can't be changed once saved. The Public API uses the key to read and write the field's values, and an import file uses the key as the column heading for the field.
  • Required: The field must be filled in whenever a vendor is created or edited. Making an existing field required doesn't affect saved vendors until they're next edited.
  • Unique: No two vendors can share a value. Matching ignores case and surrounding spaces. A field can't be made unique while vendors already share a value.
  • Status: The field's current state. A field added in the dialog shows New until you save.

Drag fields to set the order they appear on each vendor. Changes are saved together when you select Save.

Field values are text, up to 400 characters. A tenant can have up to 50 active fields.

Retiring a field hides it and its values everywhere. The values are kept, but the field can't be restored, and its key can't be reused.

Custom fields appear on the Add Vendor and Edit Vendor forms, in the Custom Fields section of each vendor's detail page, and as optional columns in the list view. My Vendors can't be sorted or filtered by a custom field.

Vendor Detail Page

The vendor detail page brings together everything you hold about one vendor: who to contact, what they have shared with you, and what you have asked them for. It opens when you click View Details on a vendor card.

The header at the top of the page shows the vendor name, the primary contact's name and email address when the vendor has a primary contact, and a Last updated date and time. The Edit Vendor and Retire Vendor buttons sit on the right of the header.

Below the header, the page shows these sections in order:

  • Custom Fields: The vendor's custom field values.
  • Contacts: The people you deal with at the vendor.
  • A KPI bar with counts for AI Cards, Bills of Materials, Compliance Frameworks, and Documents from that vendor.
  • AI Cards: The AI Cards received from the vendor.
  • AI Card Requests: The AI Card requests your organization has sent to the vendor.
  • Bills of Materials, AI Models Used, and Compliance Frameworks.

Managing Vendor Contacts

Record the people you work with at a vendor so you know who to reach and who receives your AI Card requests. Each contact in the Contacts section shows the contact's name, email address and a label for where the contact came from, such as Added by hand, Imported or From an AI Card request. The primary contact also shows a Primary tag.

Select Add contact to open the Add Contact form:

  • First Name: The contact's first name. Required.
  • Last Name: The contact's last name.
  • Email: The contact's email address. Two contacts at the same vendor can't share an email address.
  • Primary contact: Makes this person the vendor's primary contact.

To change a contact, select the pencil icon on the contact's row. The Edit Contact form has the same fields as Add Contact. To remove a contact, select the trash icon on the row. Deleting a contact is permanent.

A vendor has one primary contact. To change it, edit another contact and select Primary contact. When you save, that contact takes the Primary tag and the previous primary contact loses it. The header then shows the new primary contact.

AI Cards

The AI Cards section lists all AI Cards received from the vendor. Use the toggle on the right of the section to switch between the grid and the list. In the grid, each entry shows the AI Card name, AI System name, date sent, artifact breakdown, and current status. When the vendor shares vulnerability data on a card, the entry also shows the Vulns (N) panel with the model and technology severity charts. The list shows the AI System, Date Sent, and Artifacts for each card. The date sent is when the vendor sent the card, or N/A when that time is not known. Click View Details on any AI Card to open the AI Card detail view.

AI Card Requests Sent to This Vendor

The AI Card Requests section lists the AI Card requests your organization has sent to this vendor, so you can see what you have asked for and where each request stands. Viewing it requires permission to read AI Card requests. The table has these columns:

  • Name: The request name.
  • To: The vendor and the email address of the contact the request was sent to.
  • Date Sent: The date the request was sent.
  • Due Date: The date the response is due, or N/A when none was set.
  • Details: The request details.
  • Refresh Schedule: How often the vendor is asked to refresh the AI Card, or None.
  • Status: The request's current state, such as Pending or Completed. A completed request on a refresh schedule shows Completed · Update Pending or Completed · Update Overdue while its next update is open, and Completed otherwise.

Requests that have a due date show a due-date tag: Due in N Day(s), Due Today or Overdue. Completed requests on a refresh schedule show the tag for their next update.

Name, To, Date Sent, Due Date, Details and Status can be sorted. Use the rows menu below the table to set how many requests show on each page.

When no requests have been sent, the section shows "No linked AI Card requests have been sent to this vendor."

Bills of Materials

The Bills of Materials section displays BOM cards associated with that vendor.

AI Models Used

The AI Models Used section shows a searchable, sortable grid of AI models present across that vendor's AI Cards. Each model card displays the model name, provider, severity tag, Vulnerability Likelihood score, the number of received AI Cards containing the model, and the test status. You can sort this grid by severity from highest to lowest.

Compliance Frameworks

The Compliance Frameworks section lists the compliance frameworks included in that vendor's AI Cards along with their current status.

Reviewing an AI Card

When an AI Card has a status of Pending or Changes Requested, a Review AI Card button appears in place of the standard View Details button. Click Review AI Card to open the Review AI Card drawer. The drawer is organized into two sections:

Requested Section:

  • Request Details
  • Compliance Frameworks requested
  • Bill of Materials requirements
  • Additional Documentation requirements

AI Card Response Section (headed as "AI Card Details"):

  • AI Card Name
  • Bill of Materials included
  • Vulnerability Data: Shared or Not shared
  • Additional Documentation included
  • A Card Comparison view (shown when the card is a response to one of your outgoing requests)

At the bottom of the drawer, you have three action options:

  • Decline: Reject the AI Card
  • Request Changes: Send feedback requesting modifications to the AI Card. This opens a modal where you can compose a message to the publisher (up to 1000 characters). This option is only available when the AI Card is a response to a prior outgoing request.
  • Accept AI Card: Accept the AI Card as provided

AI Card Detail View

The AI Card detail view shows everything a vendor shared on an AI Card, so you can judge the AI System behind it. Clicking View Details on an AI Card from the vendor detail page or the View By Received AI Card grid opens it. The view is organized into tabs. Every card has Overview, Artifacts and Governance tabs. A card that shares vulnerability data also has Model Vulnerabilities and Technology Vulnerabilities tabs.

Overview

The Overview tab summarizes the card:

  • AI System: The name of the AI System the card describes.
  • Artifacts (N): The total number of artifacts on the card, with a bar and count for each type: BOMS (Bills of Materials), COMP (Compliance Frameworks), and DOCS (Documents).
  • Vuln (N): The total number of vulnerabilities on the BOMs attached to the card.

Artifacts

The Artifacts tab shows a card for each artifact the vendor included, such as a Bill of Materials, a Vulnerability Report or a Document Library file. Each artifact card shows:

  • Type: A label for the artifact type.
  • Name: The artifact name.
  • Date: The date and time the artifact was created.
  • Status: The artifact's current state, such as Completed or Failed.

Vulnerability report PDFs attached to cards published before shared vulnerability data was available remain on this tab, and you can still view and download them.

Model Vulnerabilities

The Model Vulnerabilities tab lists the vendor's shared model findings by severity.

Technology Vulnerabilities

The Technology Vulnerabilities tab lists the vendor's shared technology vulnerabilities by severity. The AI column marks vulnerabilities that affect AI components. Select Show AI vulnerabilities only to hide the rest.

Governance

The Governance tab shows the information the vendor recorded about the AI System, grouped into sections. Fields the vendor did not fill in show Not provided.

  • System Information: Purpose, Date of Initial Deployment, Last Updated and Next Regular Update.
  • Values: Value Statement and Link to Organizational Value.
  • Data: Description, Data Provenance and Data Protection.

About Shared Vulnerability Data

Shared vulnerability data is a snapshot the vendor sends when the card is published or updated. It includes CVEs, model findings, resolved findings and their resolution reasons. It doesn't include who resolved each finding, the vendor's AI System, project name or repository name. You can't act on these findings. The data refreshes only when the vendor updates the card, and you aren't notified when the vendor has newer results.

Did this answer your question?