Use the Entity Tree to explore the product entities discovered in your project and understand how they relate to one another. This helps you move from a high-level product view to the specific components, flows, and relationships that make up the product.
Overview
The Entity Tree presents discovered product intelligence in a navigable hierarchy. You can use it to review entities such as product surfaces, user flows, components, and relationship-focused findings without manually tracing every source file.
When you are investigating how an area of the product is organized, start with the Tree view. The tree is especially useful when a search result or top-level entity indicates that additional related entities exist beneath it. Expand the hierarchy to follow the relationships that connect product concepts across the application.
You can also use the entity search field to narrow the tree. For example, searching for “User Flow” can help you locate a relevant flow quickly, while searching for a phrase such as “Product Surfaces” can focus the tree on product-level findings.
📷 Screenshot pending: The Entity Tree showing the Tree view, the Search entities… field, and discovered entity entries.
Prerequisites
Before you begin, make sure that:
- You have access to the relevant project in Atloria.
- Entity discovery has completed for the project you want to review.
- You know a keyword, entity name, product area, or relationship topic you want to investigate.
- You are viewing the project’s source and product intelligence area.
- You have selected the appropriate documentation context if both User Docs and View Source are available.
Step-by-Step Instructions
-
Open the project whose discovered entities you want to explore.
-
Select Tree to open the Entity Tree view.
-
Review the top-level entities shown in the tree.
-
Click an entity name to select it and view its available details.
-
Expand an entity that has child entries to reveal related entities beneath it.
-
Continue expanding child entries until you reach the level of detail you need.
-
Select Search entities… to begin filtering the Entity Tree.
-
Enter a keyword or entity name in Search entities….
-
Review the filtered entity entries that match your search.
-
Clear the search text to return to the broader Entity Tree.
-
Select an entity such as Product Surfaces — what you actually have to investigate product-level findings.
-
Select an entity such as User Flow to investigate a discovered user journey or interaction path.
-
Select a relationship-oriented entry to understand how one entity connects to another.
-
Select Source when you need to switch from the hierarchy to the underlying source-oriented context.
-
Select User Docs when you need to return to user-facing documentation content.
📷 Screenshot pending: A user entering text in Search entities… and expanding a matching entity to view its related children.
Tips and Best Practices
-
Start broad, then narrow your investigation. Begin with top-level entries such as Product Surfaces — what you actually have, then expand into more specific entities and relationships.
-
Use the Search entities… field for exact names and distinctive phrases. Search is most effective when you use terms that appear in the discovered entity name, such as “User Flow,” “Dashboard,” or “Product.”
-
Review relationships as a chain rather than as isolated entries. Discovered relationships can describe how one item renders another, uses a hook or context, provides context, uses a store, dispatches an action, or reaches a service and model. Following the chain helps you understand both the visible product behavior and the dependencies behind it.
-
Treat similarly named entities carefully. The Entity Tree may include entities representing different levels of the product, such as a broad product surface, a component, or a relationship. Expand and inspect the surrounding hierarchy before drawing conclusions.
-
Use Tree and Source together. The Tree view helps you understand structure and relationships, while Source helps you investigate the supporting source-oriented information when you need more detail.
-
Use the documentation context intentionally. User Docs is useful when you want to connect a discovered entity to user-facing guidance. View Source is useful when you need to examine the source-oriented perspective for the selected content.
Related Pages
- Explore Source Intelligence
- Search Discovered Entities
- Analyze Entity Relationships
- Use Source View
- Create and Review User Manuals
- Use API Explorer
Troubleshooting
No entities appear in the Tree view
Confirm that you opened the correct project and that entity discovery has completed. If the project has not yet been analyzed, the Entity Tree may not contain discovered entries to explore.
Search does not show the entity you expect
Clear Search entities… and check the top-level tree first. Then try a shorter or more distinctive term, such as “Dashboard,” “User,” or “Product,” instead of a full sentence or assumed entity name.
You can see an entity but cannot understand its relationships
Expand the entity and inspect its child entries. If the hierarchy alone does not provide enough context, select Source to investigate the source-oriented view, then return to Tree to continue following the relationship structure.
Was this page helpful?