/ Docs
Settings & Customization

Business Atlas - Configuration

Last updated July 31, 2025 · View as Markdown

For overview information on the Business Atlas feature, see this article.

Prerequisites

In order to configure the Business Atlas, you will need to have Platform Configurations > View, Edit scope. This can be assigned by your Relyance Administrator.

  • Editing business entities from the vendor detail page will update the Business Atlas settings under Settings.
  • If you use a .yaml configuration file for Source Code Integration product and service definitions and you define a Business Atlas in the Relyance UI, the definitions in the UI will take precedence and be applied.

Configuration

There are two ways to configure and manage the business entity and internal product mappings: centrally, or via individual integration pages.

Method 1 - Central Configuration

You can configure the Business Atlas within the Settings menu.

  1. Login to your Relyance account which has scope Platform Configurations > View, Edit.
  2. Navigate to the Settings Menu in the bottom left-hand side.
  3. Click on the Business Atlas menu item in the Settings Menu.
  4. On this page there are two tabs, the Business Atlas tab and the Assign Vendors or Services tab:

Business Atlas tab

This is where users can:

  • Define their organizational hierarchical structure.
  • Map internal products in the context of their organizational structure.
  • Vendors, services and processing activities can be mapped to business entities and internal products.

Img1.png

  • Business entities can be mapped as sister entities, or may be arranged hierarchically.
  • Products can be mapped side-by-side to business entities, be placed under a single business entity or another product.
  • Vendors or services can be assigned to one or more business entities in a hierarchy. Vendors and services are not automatically inherited by the parent if it is assigned to the child business entity (and vice versa).

Assign Vendors or Services tab

This tab allows users to assign vendors or services to business entities, or internal products, or both.

Img2.png

  • Use the Entity Type: All Vendors and Services filters to narrow the vendors or services you want to map.

Img3.png

  • Use the Select Discovery Sources filter to narrow the associated vendor or service source you want to map (i.e., any of the four core integration types: source code, infrastructure, vendor, or contract)

Img4.png

Vendors or services can be assigned to one or more business entities clustered in a hierarchy (parent/child relationship). Vendors and services are not automatically inherited by the parent if it is assigned to the child business entity (and vice versa).

Method 2 - Integration pages

Integration configuration pages (source code, infrastructure and vendor) support internal product and business entity mapping. Once a successful source code, infrastructure, or vendor integration is configured, then the Relyance UI will support this mapping.

Source code

Relyance users are able to associate vendors and services detected by these integrations to business entities and internal products.

First One.gif

Vendor integrations & Infrastructure integrations

In most cases, only the vendor for which the integration is being configured can be associated with business entities and internal products.

Second Gif.gif