# Integration Features

### Overview

The Relyance platform enables integration with third-party SaaS tools to retrieve privacy metadata from these systems. Since SaaS vendors implement their REST APIs differently, data retrieval methods can vary, making certain vendor integrations more suitable for specific features.

### Schema Inspection (Property Scan)

By default, Relyance performs a schema inspection on third-party integrations. This involves accessing a known REST endpoint that contains PII, taking a sample, and verifying the results.

If any results are found (without reading them), it is assumed the endpoint contains PII. The Relyance algorithm records this in the integration metadata and discards the payload.

In this way, the schema inspection identifies metadata in the api schema when results are found.

These requests are READ-ONLY.

### Data Inspection

Data Inspection extends the schema inspection by analyzing and inspecting the sampled results for PII, helping to identify data in ambiguous schemas and data stores. This feature may require more permissions than the Schema Inspection for data retrieval.

In a scan with Data Inspection enabled, each finding/result has a confidence value associated with it. We map these into five categories:

| very unlikely unlikely possible (default) likely very likely |  |
| --- | --- |

![edit-find.png](https://assets.relyanceuat.xyz/images/docs/27462647156877/27462912622733.png)

The minimum likelihood setting adjusts the sensitivity of the Data Inspection feature. Lower likelihoods (e.g., unlikely) offer more coverage but may produce false positives, while higher sensitivity (e.g., very likely) provides greater accuracy but less coverage.

**Duration of QC samples**

After Data Inspection completes, results are discarded unless the Duration of QC Samples is set (default: 0 days). If set, the Relyance QC team can collaborate with your team to review the results for accuracy and completeness.

### Vendor Discovery

This feature identifies vendors within a third-party tool and automatically adds them to the Relyance Data Inventory and Map. Some vendors, such as Okta, maintain a list of vendors or service connections that are valuable for a privacy officer to know.

This feature helps identify shadow IT and unknown systems/vendors.

A vendor, once identified through vendor discovery and later removed from the connected app, will be also removed from the vendor list in Relyance. Its presence will only be retained if it is also identified through another source.

If a vendor is manually modified such as department assignment, name and etc. It will no longer be automatically removed, even if its discovery sources is lost.

### Contract Scan

This feature downloads contracts from the integrations file repository. These contracts will then be analyzed by Relyance NLP to identify key clauses found in those contracts. Please see this article for information on the types of contracts Relyance analyzes: [Understanding the Types of Contracts Ingested by Relyance](/docs/introduction-to-relyance-ai/understanding-the-types-of-contracts-ingested-by-relyance/).

### Asset Discovery

This feature indicates you wish to scan this integration using Relyance's Asset Intelligence module. The Asset Intelligence module enhances visibility into organizational commitments and obligations, providing tools to monitor and visualize data assets, assess security postures, and manage compliance risks effectively.

### Data Subject Requests

When this is enabled, it allows your Data Subject Requests (DSRs) workflows to use this integration when responding to data subject requests. Typically, expanded permissions are needed for these requests which are found at the bottom of the integration configuration page.

This feature requires write permissions in the case of DELETE requests.