---
title: 04.05 Managing Vendors in SimpleRisk
description: Keep a list of your third-party vendors next to your assets and risks. Add a vendor, move it through its status lifecycle, link it to the assets, asset…
---

[Skip to content](https://support.simplerisk.com/kb/04-05-managing-vendors-in-simplerisk#main-content)

English

Show submenu for translations

[Customer portal](https://support.simplerisk.com/tickets?hsLang=en)

[![SimpleRisk logo of a man walking a tight rope](https://support.simplerisk.com/hs-fs/hubfs/simplerisk_logo_long_small-4.png?width=377&height=72&name=simplerisk_logo_long_small-4.png)](https://www.simplerisk.com/)

Open main navigation

Close main navigation

- English
  
  Show submenu for translations
- [Customer portal](https://support.simplerisk.com/tickets)
- [Contact us](https://www.simplerisk.com/about-us/contact-us)

[Contact us](https://www.simplerisk.com/about-us/contact-us)

 How can we help you?

- There are no suggestions because the search field is empty.

1. [SimpleRisk Knowledge Base](https://support.simplerisk.com/kb?hsLang=en)
2. [User Guide](https://support.simplerisk.com/kb/user-guide?hsLang=en)
3. [04 Asset and Data Inventory](https://support.simplerisk.com/kb/user-guide?hsLang=en#04-asset-and-data-inventory)

# 04.05 Managing Vendors in SimpleRisk

## Keep a list of your third-party vendors next to your assets and risks. Add a vendor, move it through its status lifecycle, link it to the assets, asset groups and risks that depend on it, control who sees it with teams, and understand the locked pages and tabs the Vendor Risk Management Extra fills in.

## Why this matters

Every system in your asset inventory depends on somebody. The payroll platform is a SaaS subscription, the customer database runs in a cloud provider's region, and the badge readers were installed by a facilities contractor who still has remote access. When one of those suppliers has a breach or an outage, the first question is always the same: which of our systems and which of our risks does this touch? If the answer lives in a procurement spreadsheet, you'll spend the first hour of the incident building it.

The NIST Cybersecurity Framework (CSF) 2.0 gives supply chain risk management its own category under the Govern function, and ISO/IEC 27001:2022 spends several Annex A controls on supplier relationships. Both start from the same place: a list of your suppliers that's tied to what they support. SimpleRisk keeps that list as part of the asset and data inventory. A vendor has a profile, a status, the teams that may see it, and links to the assets, asset groups and risks that depend on it.

That much is part of SimpleRisk itself. The Vendor Risk Management Extra builds on the same vendor record with intake questionnaires, risk tiers, contacts and a computed risk score. Without the Extra, those parts of the menu and the vendor page show as locked, so you can see what's there without being sent to a page that doesn't exist.

## Before you start

- **The Vendor Risk menu.** You need **Allow Access to "Vendor Risk" Menu**. Without it there's no **Vendor Risk** entry in the left menu and no **Vendors** field on assets or risks.
- **Permission for what you want to change.** **Able to Add Vendors** shows the **+ New vendor** button. **Able to Edit Vendors** lets you edit a vendor's profile and change its status. Saving a vendor's linked assets also needs **Able to Edit Assets**. **Able to Delete Vendors** shows **Delete vendor**. Each of them works only together with the menu permission.
- **Access to the things you link.** The **Assets** tab needs **Allow Access to "Asset Management" Menu**, and the **Risks** tab needs **Allow Access to "Risk Management" Menu**. Without them the tab isn't shown.
- **Your vendor categories and data types.** An administrator keeps these two lists in **Add and Remove Values**, under **Vendor Categories** and **Vendor Data Types**. Ask for a missing category rather than filing everything under "Other".

## Step-by-step

### 1. Open Manage Vendors

Select **Vendor Risk** in the left menu, then **Manage Vendors**. The list shows each vendor's **Name**, **Category**, **Status**, **Business Owner** and **Last Updated** date. The **Columns** button lets you show or hide any column except **Name**; your choice applies at once and is remembered for your account, and **Restore default layout** undoes it. On a narrow window the columns you haven't touched drop out by themselves; open the vendor to see everything.

Type in **Search vendors** to match the vendor name or legal name. The **All statuses**, **All categories** and **All owners** filters narrow the list, and a column heading sorts it. The **All owners** filter offers the people who are the business owner of at least one vendor you can see. You can also select a vendor's status, category or business owner in the table itself: the list narrows to that value. Selecting a value only ever adds a filter. To take one off, choose **All statuses**, **All categories** or **All owners**, or select **Clear filters**, which appears beside the filters whenever a filter or the search is in use and also empties the search box. On a small screen the filters sit behind a **Filters** button. Everything you set, including the search text, the sort and the page, is kept in the address bar, so you can copy the link to share a filtered view or come back to it later. A link value that doesn't exist on your instance is simply ignored. When nothing matches, **Clear filters** brings the full list back, too. **Show** sets how many rows appear per page.

### 2. Add a vendor

1. Select **+ New vendor**. The form opens in a dialog over the list.
2. Enter the **Name**. It's the only required field, it can be up to 255 characters, and it has to be unique across the installation, ignoring capitals.
3. Fill in what you know. **Legal name** is the contracting entity when it differs from the trading name. **Website** has to start with `http://` or `https://`. **Category** and **Business Owner** are optional.
4. Choose a **Status**: a new vendor starts as **Prospect** or **Onboarding**.
5. Pick the **Team(s)** that should see the vendor, the **Vendor Data Types** it will handle, and any **Tags**.
6. Select **Save**. The dialog closes and the new vendor opens on its Profile tab.

Type a tag and press Enter or a comma to add it, and select the small x on a tag to remove it. A vendor can carry up to 50 tags, and a tag you've already added is ignored whatever its capitalisation.

Be generous with **Vendor Data Types**. "Which of our vendors touch personal data?" is the question auditors ask most, and trimming a list later is easier than rediscovering what you left off.

If you see *The specified name is already in use.*, another vendor has that name. It may be one you can't see, because under team separation vendors in other teams are hidden from you. Choose a name that includes the legal entity, or ask an administrator.

### 3. Edit the profile

Open a vendor by selecting its name. The **Profile** tab shows the details you entered plus the **Last Updated** date. Select **Edit** to change them and **Save** when you're done. The status isn't on the edit form; it has its own card.

**Back to vendors** returns you to the list. If you got to the vendor from **Conduct Due Diligence**, **Manage Contracts**, **Manage Findings** or one of the Vendor Risk reports, the link instead names that page, for example **Back to Manage Findings**, and takes you back to it with its filters as you left them.

### 4. Move the vendor through its lifecycle

A vendor's status is one of **Prospect**, **Onboarding**, **Active**, **Offboarding** or **Terminated**. If you can edit vendors, the **Change Status** card on the **Profile** tab offers the moves allowed from the current status, and **Apply** makes the change.

- **Prospect:** Onboarding, Terminated
- **Onboarding:** Active, Terminated
- **Active:** Offboarding
- **Offboarding:** Terminated, Active
- **Terminated:** Nothing. The card says *No further status changes are possible.*

Without the Vendor Risk Management Extra, **Able to Edit Vendors** is all it takes to make a vendor Active or to terminate it. With the Extra active, Active also needs a risk tier and an approver; [Using the Vendor Register](https://support.simplerisk.com/kb/06-05-the-vendor-register?hsLang=en) explains how. Moving a vendor from Offboarding to Terminated also needs **Able to Approve Vendors** and a started offboarding checklist with every required step done; [Vendor Findings and Offboarding](https://support.simplerisk.com/kb/06-09-vendor-findings-and-offboarding?hsLang=en) walks through it.

Terminated is final. If a relationship might resume, park the vendor in Offboarding instead.

### 5. Link assets and asset groups

Open the **Assets** tab. This is where you answer "what's affected if this vendor has a bad day?"

If you can edit vendors and assets, the tab has one picker for both assets and asset groups, the same one you use for a risk's affected assets. Open the list, choose an asset or an asset group, and each choice appears as a chip: assets and asset groups are shown in different colors, and the list groups them under **Standard Assets** and **Asset Groups**. Remove a chip with the small x on it, then select **Save**. You can only pick records that already exist. Without both edit rights you see the same chips with no x and no **Save**, or *No linked assets.*

You only see the assets you'd see in the asset list. When a vendor is linked to assets hidden from you, the tab says *Links to assets you cannot see are kept when you save.* Saving never removes someone else's links.

One save can add at most 200 new links. A vendor that already has more than that, often from links made on the assets themselves, still saves normally. To link a few hundred assets at once, add them in batches and save after each.

Link asset groups where you can. A vendor that hosts "everything in the payments platform" is easier to keep current as one group than as forty assets.

### 6. See the linked risks

The **Risks** tab lists, under **Linked risks**, each risk tied to the vendor with its ID and subject. Select an ID to open the risk. It's read-only: you link a risk to a vendor from the risk itself (step 7), the same way you tie a risk to its assets. Risks you aren't allowed to see aren't listed.

### 7. Use the Vendors field on assets and risks

Assets and risks carry a **Vendors** field in their **Additional Information** section, where you can pick one or more vendors.

- **On an asset**, the field is in the asset window: in **Add asset**, and in edit mode for anyone who can edit assets. In view mode it shows the linked vendors as links to their pages.
- **On a risk**, the field is on the **Submit Risk** form, and in the **Details** tab once you select **Edit Details**, if you can modify risks. The risk's view shows the linked vendors the same way.

The picker lists the vendors you can see, 50 at a time. When there are more, a search box appears so you can find the rest. A link to a vendor you can't see stays in place when you save.

On a new asset or risk, the vendors travel with the record. If one of them can't be linked, nothing is saved and the form tells you why. One message surprises people: *The record was not saved: vendors can only be linked to a record you can see, and the teams you chose would hide this one from you.* It means the teams on the new asset would put it out of your own reach, so choose a team you belong to.

On an existing asset or risk, the vendors save just after the rest of the record. If that second save fails, the record keeps its other changes and the field says *The record was saved, but its vendors were not. Save the vendors again.* with your choices still selected. Fix the problem it names and save again.

The field only appears for users with the Vendor Risk menu permission. Everyone else sees the asset or risk without it, and their saves leave its vendor links alone.

### 8. Control who sees a vendor

Teams on a vendor restrict who sees it only when your administrator uses the Team-Based Separation Extra. Then:

- administrators see every vendor;
- a vendor with no teams is visible to everyone who can open Manage Vendors;
- any other vendor is visible only to members of at least one of its teams.

Under separation, a non-administrator has to put a new vendor in at least one of their own teams (*Choose at least one team.*). When you edit a vendor's teams you only manage your own part of the list. Teams you don't belong to stay as they were, and the vendor must still end up with at least one team. If you take off all of your own teams while other teams remain, the save goes through and the page tells you *The vendor was updated. Its teams no longer include yours, so you can no longer see it.*

A vendor you can't see behaves as if it didn't exist, on the page, in the **Vendors** field and in the Connectivity Visualizer.

### 9. Follow a vendor in the Connectivity Visualizer

Vendors appear in the **Connectivity Visualizer** report as their own node type, linked to their assets, asset groups and risks. Start from an asset or a risk and the vendors it depends on show up as neighbours; select a vendor to see everything else it touches. That's the quickest way to scope a vendor incident. Hidden vendors, and their links, are left out.

Two limits in this release. You reach a vendor through something linked to it, because the report doesn't let you search for or browse vendors directly. And opening the report takes access to the Risk Management, Governance, Compliance or Asset Management menu, or **Able to View Exceptions**, so a user who holds only the Vendor Risk menu can't open it.

### 10. Delete a vendor

On the vendor's page, select **Delete vendor** and confirm. The warning reads *Deleting this vendor removes it and its links to assets and risks. This cannot be undone.* When the Vendor Risk Management Extra is active, the warning adds what the Extra loses too. For a vendor you no longer use, moving it to Terminated keeps the record and its links, which is usually what an auditor wants to see.

## What the locked pages and tabs mean

Without the Vendor Risk Management Extra, the **Vendor Risk** menu shows **Manage Vendors** first, then four locked entries in this order: **Onboard Vendors**, **Conduct Due Diligence**, **Manage Contracts** and **Manage Findings**. The vendor dashboard and reports aren't offered at all without the Extra. A vendor's page shows **Profile**, **Assets** and **Risks**, then locked **Tier**, **Contacts**, **Monitoring**, **Assessments**, **Evidence**, **Contracts**, **Findings** and **Dependencies** tabs with a padlock.

Opening a locked entry or tab shows a card marked **Locked** with one sentence about what the Extra adds. What follows depends on who you are:

- A non-administrator sees *An administrator can set this up.*
- An administrator sees *Requires the Vendor Risk Management Extra.* with a **See what it adds** link.
- If the Extra is installed but switched off, an administrator sees *The Vendor Risk Management Extra is installed but not turned on.* with a **Turn it on** link.

Nothing you enter in Manage Vendors is lost when the Extra arrives. It works on the same vendors, with the same links, and adds its own tabs to the same page.

## Common pitfalls

- **Creating the same vendor twice.** "Acme", "Acme Inc." and "ACME Corporation" are three vendors to the uniqueness check. Agree on a naming convention, such as the legal name's short form, and search before you add.
- **Linking from the wrong side.** Risks are linked from the risk's **Vendors** field; the vendor's **Risks** tab only lists them. Assets can be linked from either side.
- **Expecting teams to hide vendors without team separation.** They don't. If vendor details are sensitive, ask your administrator about the Team-Based Separation Extra before you load vendors.
- **Leaving a vendor without a team under separation.** A teamless vendor is visible to everyone who can open Manage Vendors, the opposite of what most people expect.
- **Deleting instead of terminating.** Delete removes the vendor and every link to it. Terminated keeps the history.
- **Treating Prospect as "not our problem".** A prospect that's already processing your data in a pilot is a live risk. Move it to Onboarding as soon as real data is involved.

## Related

- [Managing Assets in SimpleRisk](https://support.simplerisk.com/kb/04-02-managing-assets-in-simplerisk?hsLang=en)
- [Tying Risks to Assets](https://support.simplerisk.com/kb/04-04-tying-risks-to-assets?hsLang=en)
- [Using the Vendor Register](https://support.simplerisk.com/kb/06-05-the-vendor-register?hsLang=en)
- [Vendor Intake and Tiering](https://support.simplerisk.com/kb/06-06-vendor-intake-and-tiering?hsLang=en)
- [Vendor Findings and Offboarding](https://support.simplerisk.com/kb/06-09-vendor-findings-and-offboarding?hsLang=en)
- [Vendor Overview, Reports and Control Coverage](https://support.simplerisk.com/kb/06-10-vendor-overview-reports-and-control-coverage?hsLang=en)
- [The Vendor Risk Management Extra](https://support.simplerisk.com/kb/12-09-the-vendor-risk-management-extra?hsLang=en) in the Administrator Guide
- [Permission Reference](https://support.simplerisk.com/kb/03-03-permission-reference?hsLang=en) in the Administrator Guide

- [FAQs](https://support.simplerisk.com/kb/faqs?hsLang=en)
- [SimpleRisk Extras](https://support.simplerisk.com/kb/simplerisk-extras?hsLang=en#main-content)

    - [Vulnerability Management Extra](https://support.simplerisk.com/kb/simplerisk-extras?hsLang=en#vulnerability-management-extra)
    - [Team Separation Extra](https://support.simplerisk.com/kb/simplerisk-extras?hsLang=en#team-separation-extra)
    - [Import-Export Extra](https://support.simplerisk.com/kb/simplerisk-extras?hsLang=en#import-export-extra)
- [Administrator Guide](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#main-content)

    - [00 About This Guide](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#00-about-this-guide)
    - [01 Installation and Deployment](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#01-installation-and-deployment)
    - [02 Upgrades and Maintenance](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#02-upgrades-and-maintenance)
    - [03 Users and Permissions](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#03-users-and-permissions)
    - [04 Authentication](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#04-authentication)
    - [05 Customization](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#05-customization)
    - [06 Configuring Risk and Compliance](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#06-configuring-risk-and-compliance)
    - [07 Integrations](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#07-integrations)
    - [08 The API](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#08-the-api)
    - [09 Encryption and Data Security](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#09-encryption-and-data-security)
    - [10 Workflows and Automation](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#10-workflows-and-automation)
    - [11 Reporting and Auditing](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#11-reporting-and-auditing)
    - [12 Operations](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#12-operations)
    - [13 Reference](https://support.simplerisk.com/kb/administrator-guide?hsLang=en#13-reference)
- [User Guide](https://support.simplerisk.com/kb/user-guide?hsLang=en#main-content)

    - [00 Foundations of GRC](https://support.simplerisk.com/kb/user-guide?hsLang=en#00-foundations-of-grc)
    - [01 Risk Management](https://support.simplerisk.com/kb/user-guide?hsLang=en#01-risk-management)
    - [02 Compliance Management](https://support.simplerisk.com/kb/user-guide?hsLang=en#02-compliance-management)
    - [03 Governance](https://support.simplerisk.com/kb/user-guide?hsLang=en#03-governance)
    - [04 Asset and Data Inventory](https://support.simplerisk.com/kb/user-guide?hsLang=en#04-asset-and-data-inventory)
    - [05 Threat and Vulnerability Management](https://support.simplerisk.com/kb/user-guide?hsLang=en#05-threat-and-vulnerability-management)
    - [06 Assessments](https://support.simplerisk.com/kb/user-guide?hsLang=en#06-assessments)
    - [07 Incident Management](https://support.simplerisk.com/kb/user-guide?hsLang=en#07-incident-management)
    - [08 Audit and Reporting](https://support.simplerisk.com/kb/user-guide?hsLang=en#08-audit-and-reporting)
    - [09 Day-to-Day SimpleRisk](https://support.simplerisk.com/kb/user-guide?hsLang=en#09-day-to-day-simplerisk)
    - [10 Continuous Improvement](https://support.simplerisk.com/kb/user-guide?hsLang=en#10-continuous-improvement)
    - [11 Business Continuity and Disaster Recovery](https://support.simplerisk.com/kb/user-guide?hsLang=en#11-business-continuity-and-disaster-recovery)
- [SimpleRisk User Guides](https://support.simplerisk.com/kb/simplerisk-user-guides?hsLang=en)
- [Troubleshooting](https://support.simplerisk.com/kb/troubleshooting?hsLang=en)
- [SimpleRisk Hosted](https://support.simplerisk.com/kb/simplerisk-hosted?hsLang=en)
- [How To videos](https://support.simplerisk.com/kb/how-to-videos?hsLang=en)

[![favicon-1](https://support.simplerisk.com/hs-fs/hubfs/favicon-1.png?width=35&height=35&name=favicon-1.png "favicon-1")](https://www.simplerisk.com)

<https://www.facebook.com/simplerisk/> <https://www.twitter.com/simpleriskfree/> <https://www.linkedin.com/company/simplerisk/>

Copyright © 2026, SimpleRisk, Inc.