EntityTree: Exploring Product Entities

page

5 min readUpdated 2026-07-20

EntityTree helps you explore the entities that make up your product model and see how they relate to one another. Use it when you need to understand a product area, trace relationships between entities, or locate a specific entity before reviewing its source context.

Overview

EntityTree presents product entities in a browsable hierarchy. It is designed to help you move from a broad product view to individual entities without needing to search through every repository or document manually.

You can use the tree to explore product surfaces, user-facing flows, documentation topics, and other discovered entities. For example, the entity list may include items such as Product Surfaces — what you actually have, User Flow, or Browse Repositories. These entries provide a starting point for understanding how parts of the product are organized.

EntityTree is especially useful during source and product intelligence work. Start with a known product concept, use Search entities… to narrow the list, and then review the entity’s relationships to understand how it connects to other parts of the product model.

📷 Screenshot pending: The EntityTree view showing the Product area, the Search entities… field, and a hierarchy of product entities.

Prerequisites

Before you begin, make sure that:

You have access to the relevant Atloria project.
Product entities have been discovered or added to the project model.
You know a product term, screen name, user flow, or documentation topic you want to investigate.
You have permission to view product intelligence and source-related information where applicable.
You understand whether you are looking for a user-facing product entity or its supporting source context.

Step-by-Step Instructions

Open the project where you want to explore the product model.
Select Product to work with product-focused entities rather than source-focused information.
Locate the Search entities… field above the entity list.
Enter a keyword that identifies the entity you want to find.
Review the filtered entity results shown in the tree.
Select an entity name to make it the focus of your exploration.
Expand the selected entity’s branch when an expansion control is available.
Review the child entities displayed beneath the selected entity.
Select a related entity in the branch to follow the relationship from one product concept to another.
Continue expanding related entries until you reach the level of detail you need.
Use View Source when you need to compare the product entity with its available source context.
Select Source to switch your attention from the product model to the related source-oriented view.
Return to Product when you want to continue exploring product relationships.
Select User Docs when the entity relates to user documentation or a user-facing manual topic.
Select 📋 User Manuals when you want to locate user-manual content associated with the product area you are exploring.

📷 Screenshot pending: A user entering a term in Search entities… and expanding matching entities to review related product concepts.

Example: Explore a repository browsing flow

Enter Browse in Search entities….
Select Browse Repositories from the matching results.
Expand the entity branch to review related entries.
Select Browse Repos if it appears as a related entity or alternate product label.
Select 3. Repo Browser to examine the product area associated with repository browsing.
Select User Flow to understand the flow-oriented context connected to the repository browsing experience.
Select View Source if you need to investigate supporting source information for the selected product entity.

📷 Screenshot pending: The EntityTree filtered for Browse, with Browse Repositories, Browse Repos, and 3. Repo Browser visible in the relationship hierarchy.

Tips and Best Practices

Start with the most specific term you know. Searching for a screen or feature name, such as Repo Browser, usually produces more focused results than a broad term such as “product.”
Try alternate names when an entity does not appear immediately. A concept may be represented with a user-facing label, a shorter label, or a broader product-area name. For example, Browse Repositories and Browse Repos may both be useful search terms.
Explore both parent and child entries. A parent entity gives you context for where an item belongs, while child entities can reveal more detailed product concepts and supporting relationships.
Treat relationships as navigation paths, not just a list. If an entity leads to User Flow, use that connection to understand the user journey. If it leads to documentation topics, use User Docs or 📋 User Manuals to investigate the user-facing guidance.
Use Product and Source together when needed. The Product view helps you understand what users experience; Source helps you investigate the available implementation context. Switching between them can clarify whether two similarly named entities refer to the same product capability.
Search for documentation-oriented entities when researching product guidance. Entries such as Product Surfaces — what you actually have or Lane ③ — User manuals / help centers / KBs can help you identify relevant manual and help-center coverage.

Troubleshooting

No entities appear after searching

Clear the text in Search entities….
Enter a shorter or alternate keyword.
Try a related product term, such as Product, User Flow, or Source.
Confirm that you are working in the correct project.

The entity I found does not show the relationship I expected

Expand the entity’s available branch.
Select its parent entity to review the broader context.
Select related child entities to follow adjacent product concepts.
Use View Source to review source context when the product relationship alone is not enough to explain the connection.

I cannot tell whether I should use Product or Source

Select Product when you want to understand screens, product areas, user flows, or documentation-facing concepts.
Select Source when you need to investigate the available source context for an entity.
Return to Product after reviewing source information to continue mapping the entity’s product relationships.

Was this page helpful?

Download as PDF

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