Configure Relationship Visibility

page

4 min readUpdated 2026-07-20

This page explains how to prepare a project for relationship visibility configuration in Atloria. Relationship visibility affects how you explore connections between entities in a project, helping users focus on the relationships that matter for their current review.

Overview

Relationships represent connections between entities in a product model. When relationship visibility is configured appropriately, project explorers can present a clearer view of related items and reduce distractions from connections that are not relevant to a particular review.

You typically configure relationship visibility when you are preparing a project for technical documentation, model review, change analysis, or stakeholder exploration. Before changing visibility settings, make sure you are working in the correct project, because relationship presentation is relevant to the focused project rather than the overall project list.

Atloria provides project navigation from the Projects area. From there, you can search for a project, open its dashboard, and continue to the project areas used for exploration and documentation.

📷 Screenshot pending: Relationship exploration view showing entities and their visible relationships.

Prerequisites

Before you begin, make sure that:

You can access the Projects area.
The project you want to configure already exists.
You know the project name or can locate it by using Search projects....
The project contains analyzed entities and relationships to explore.
You have the appropriate administrator or project-management permissions for the project.
You understand which relationships should be emphasized or hidden for the intended audience.

Step-by-Step Instructions

Select Projects to open the list of available projects.
Use Search projects... to find the project whose relationship presentation you want to review.
Select the matching project from the search results to make it the active project.
Select Open Project Dashboard to open the focused project workspace.

📷 Screenshot pending: The Projects page with a selected project and the Open Project Dashboard action.

Open the project area used for product-model exploration or technical documentation.
Locate the relationship or entity exploration panel for the active project.
Review the entities displayed in the exploration panel before changing any visibility option.
Identify the relationship types that users need to see during project exploration.
Identify relationship types that should not appear in the current exploration context.
Open the relationship visibility controls when they are available in your project’s exploration interface.
Select the visibility option for each relationship type you want to present to users.
Clear the visibility option for each relationship type you do not want to present.
Review the updated entity relationships in the exploration view.
Save or apply the visibility changes if the screen provides a save or confirmation action.
Return to the project exploration view and verify that the visible relationship paths match the intended model view.

📷 Screenshot pending: Relationship visibility controls with relationship types selected or cleared for project exploration.

Important: The available evidence confirms project navigation labels such as Projects, Search projects..., and Open Project Dashboard. The specific relationship-visibility control labels and save behavior should be confirmed in your Atloria environment before publishing organization-specific instructions or training materials.

Tips and Best Practices

Configure visibility for a specific exploration purpose. For example, a documentation reviewer may need broad relationship visibility, while a stakeholder review may benefit from a smaller set of business-relevant connections.
Start with the most important relationship types visible. This makes it easier to confirm that users can follow the primary paths through the product model before adding secondary relationships.
Review visibility changes in the exploration view immediately after applying them. A relationship type can be correctly selected in a configuration panel but still produce an overly complex model view when many entities use that relationship.
Use the project search when you manage many projects. The Search projects... field helps you avoid opening and configuring the wrong project.
Confirm that you are in the focused project workspace before making changes. Selecting Open Project Dashboard after choosing the project helps ensure you are reviewing the intended project context.
Coordinate visibility decisions with your documentation and architecture owners. Relationship visibility affects how users interpret the structure of the model, so inconsistent settings can make different project views harder to compare.

Troubleshooting

You cannot find the project to configure

Select Projects.
Enter part of the project name in Search projects....
Confirm that you are searching the correct project list.
If the project is not listed, verify that the project has been created and that you have access to it.

You opened a project but cannot find relationship visibility controls

Select Open Project Dashboard to confirm that you are in the focused project workspace.
Open the project’s product-model, entity, or technical-documentation exploration area.
Check whether relationships have been generated for the project.
Ask a project administrator to confirm whether your role includes permission to change relationship presentation settings.

Relationship changes do not appear in exploration

Review the selected relationship types in the relationship visibility controls.
Confirm that the active project contains entities using those relationship types.
Apply or save the changes if the interface provides a confirmation action.
Refresh the exploration view and check the relationship paths again.

Was this page helpful?

Download as PDF

ADocs generated by Atloria — from the code, always in sync →