# Explore the Entity Relationship Graph Use **View Graph** to examine product entities and the relationships between them. This helps you understand how parts of the product connect before you review source details or create documentation. ## Overview The Entity Relationship Graph provides a visual way to explore the entities discovered for a product and the connections between them. Instead of reviewing entities one at a time, you can use the graph to see relationship paths such as components that render other components, components that use hooks, or entities that depend on services. Use the graph when you need to understand the scope of a product area, trace how an entity is connected to other entities, or identify related items for further review. The graph is especially useful when an entity participates in multiple relationships, such as rendering another component while also using a hook or context. The graph complements the entity search and source review tools. You can first locate a specific item with **Search entities…**, open the graph with **View Graph**, and then use **View Source** when you need to inspect the supporting source information for an entity. > 📷 _Screenshot pending: The Entity Relationship Graph opened from the View Graph action, showing entities and their connecting relationships._ ## Prerequisites Before you start, make sure that: - You can access the relevant product or project in Atloria. - The product has entities available for review. - You know the entity, feature area, or relationship you want to investigate. - You have access to the actions **View Graph**, **View Source**, and **Search entities…**. - You have reviewed the product’s **Overview** if you need context before exploring relationships. ## Step-by-Step Instructions 1. Open the product or review area that contains the entities you want to investigate. 2. Select **Product** to work with the product-level entity information. 3. Enter an entity name or relevant keyword in **Search entities…** to narrow the available entities. 4. Select the entity you want to investigate from the search results or entity list. 5. Click **View Graph** to open the Entity Relationship Graph for the selected product context. 6. Review the entity nodes shown in the graph to identify the entity you selected and the entities connected to it. 7. Read the relationship labels between nodes to understand how the connected entities relate to each other. 8. Follow a connection from the selected entity to identify directly related entities, such as a component that **RENDERS** another component or **USES HOOK**. 9. Select a connected entity in the graph when you want to continue investigating that entity’s relationships. 10. Review the next set of connections to trace a relationship chain, such as a component using a hook, the hook using context, and the context providing values through a provider. 11. Click **View Source** when you need to examine the source information associated with an entity you identified in the graph. 12. Return to **View Graph** after reviewing source information to continue tracing connections. > 📷 _Screenshot pending: A selected entity in the graph with labeled connections to related entities, including relationship types such as RENDERS and USES HOOK._ ## Tips and Best Practices Start with a focused question. For example, you might want to find what a component renders, determine which entities use a specific hook, or trace a dependency from a page to a service. Beginning with one entity makes large relationship networks easier to interpret. Use the relationship label as the meaning of the connection. A relationship such as **RENDERS** indicates a display relationship between entities, while **USES HOOK**, **USES CONTEXT**, and **PROVIDES CONTEXT** help you follow how shared behavior or data is connected. Other relationships, such as **DEPENDS ON**, **USES SERVICE**, and **QUERIES MODEL**, help you understand dependency paths across the product. Trace one connection at a time. A long chain may move through several kinds of entities—for example, from a frontend entity through a component and hook, then onward to context, a provider, a store, controller, service, repository, middleware, or model. Review each relationship label before moving to the next entity so that you do not mistake an indirect connection for a direct one. Use **Search entities…** before opening **View Graph** when the product contains many entities. Searching first gives you a clear starting point and reduces the time needed to locate the relevant area of the graph. Use **View Source** only after the graph identifies an entity or relationship that needs closer review. The graph is best for discovering connections; source review is best for validating the details behind a connection. ## Related Pages - [Search Product Entities](#) - [View Entity Source Information](#) - [Review Product Overview](#) - [Use User Docs](#) - [Explore API Documentation with API Explorer](#) ## Troubleshooting ### You cannot find the entity you want to inspect Use **Search entities…** with a more specific entity name or keyword. If no matching entity appears, return to **Overview** to confirm that you are working in the correct product or review context. ### The graph has too many connected entities to interpret easily Begin again with the specific entity most relevant to your question. Follow only its direct connections first, then select one related entity at a time to continue the relationship trace. ### You need more detail than the graph provides Select the relevant entity and click **View Source**. Use the source view to review the supporting information, then return to **View Graph** to continue exploring related entities.