# Overview and Implementation Guide

## About this document set

This is the entry point to the Relyance Inventory documentation. Start here, then go to the guide that matches what you need to do:

| Document | Audience | What's in it |
|---|---|---|
| **Overview and Implementation Guide** (this doc) | Everyone | What the Inventory is, what it contains, and how to get started |
| [Inventory Management Guide](/docs/inventory/inventory-management-guide/) | Privacy, security, GRC, and AI governance teams | Working the Inventory screen - the **Type** panel, search, filters, columns, views, drawers, and creating a policy from a filter |
| [Vendors and Technologies](/docs/inventory/vendors-and-technologies/) | Privacy Managers, vendor and third-party risk teams | Marking a vendor as a technology in your own stack, and what changes when you do |
| [FAQ: Inventory](/docs/inventory/faq-inventory/) | Prospects, new customers, sales and CS | Common questions in plain language |

## What is the Inventory?

The Inventory is one searchable list of everything Relyance has discovered in your environment - your data assets, cloud infrastructure, code repositories, services, AI agents, AI models, MCP servers, and the vendors you share data with. Instead of switching between separate lists, you see every type side by side, filter them on the same fields, and open any row for its details.

You find it under **Observe → Inventory** in the left navigation, where the unified Inventory is enabled for your tenant.

> **Note.** The unified Inventory described here is available where enabled for your tenant. If your **Inventory** page shows a single grid with **All**, **Vendors**, and **Services** pills at the top instead of a **Type** panel, it isn't enabled yet - contact your Relyance account team to turn it on.

For every item, the Inventory shows the same core facts, whatever its type:

- **What it is** - its **Name**, **Type**, and **Description**.
- **What's wrong with it** - its open **Findings** and **Risks**.
- **What data it touches** - **Data Elements**, **Data Subjects**, **Data States**, and **Classifications**.
- **Where it is and who owns it** - **Location**, **Products**, **Business Entities**, **Context**, and **Tags**.
- **Its state** - lifecycle **Status**, **Governance Status**, and when it was **Last Discovered**.

## What's in the Inventory

The **Type** panel on the left of the screen lists every type in your inventory, with a count for each. The types you see depend on what you've connected:

| Type | What it is |
|---|---|
| **AI Agents** | AI agents your organization builds or uses, split into **First Party** and **Third Party** |
| **AI Models** | Models in use - **LLMs**, **Embeddings**, and **ML Models** |
| **Assets** | Data assets - databases, tables, buckets, objects, endpoints, log groups, and more |
| **Code Repositories** | The repositories Relyance scans |
| **Infrastructure** | Cloud infrastructure such as networks, clusters, and node pools |
| **MCP Servers** | Model Context Protocol servers your agents connect to |
| **Services** | Your own internal services |
| **Vendors** | Third parties that receive or process your data |

Some types expand into sub-types - for example, **Assets** breaks down into **Databases**, **Tables**, **Buckets**, and so on.

A vendor can also be marked as a **technology** - a framework, library, or database in your own stack rather than a third party that receives personal data. See [Vendors and Technologies](/docs/inventory/vendors-and-technologies/).

## How it relates to the rest of the platform

The Inventory brings together items that also have their own focused pages. Each row opens the same detail drawer you see on those pages, so a change you make in one place shows everywhere.

| To work with... | The focused page is... |
|---|---|
| Data assets in depth | **Observe → Assets** |
| Identities and who can reach your data | **Observe → Identities** |
| AI agents, models, and MCP servers | **Observe → AI** |
| Vendors - adding, bulk editing, and exporting | **Manage → Vendors** |
| Your products and services | **Manage → Products & Services** |

## Where the data comes from

You don't build the Inventory by hand. Relyance populates it and keeps it current from your connected sources:

- **Integrations** - cloud accounts, data stores, identity providers, SaaS apps, and observability tools. See [How Integrations Work](/docs/integrations/).
- **Source code** - repository scans find your services, the third-party services and SDKs your code calls, and the AI agents, models, and MCP servers it uses. See [Source Code & CI](/docs/source-code/).
- **Contracts** - agreements ingested from your contract systems. See [Contract Systems](/docs/contract-systems/).

The **Discovery Source** filter shows which source found an item, and the **Last Discovered** column shows when a scan last saw it.

## Getting started

1. **Connect your sources.** The more integrations and repositories you connect, the more complete the Inventory is.
2. **Get the lay of the land.** Open **Observe → Inventory** and read the counts in the **Type** panel. They tell you at a glance how many assets, services, vendors, and AI components Relyance has found.
3. **Look for what matters.** Filter on **Data Elements** or **Classification** to find everything that handles sensitive data, then look at the **Findings** and **Risks** columns to see where to start.
4. **Clean up vendors.** Open the **Vendors** type and mark components of your own stack as technologies.
5. **Turn a filter into a policy.** When a filter describes something that should never happen, click **Create Policy** so Relyance keeps watching for it.
6. **Save the views your team uses.** Save filtered views so they are one click away.

The [Inventory Management Guide](/docs/inventory/inventory-management-guide/) covers each of these steps in detail.
