# CapturedFlows: Documenting Captured Product Flows CapturedFlows help you review recorded product journeys and turn observed user interactions into clear documentation. Use them when you need to understand how a user moves through a product experience before writing or reviewing a User Guide. ## Overview A CapturedFlow brings together the screens and interactions that make up a product journey. Instead of documenting an isolated screen, you can use the flow to follow the user’s path from one action to the next and identify the purpose of each step. This is especially useful when you are preparing documentation for a feature with multiple screens, such as creating a record, reviewing information, and publishing or exporting documentation. Reviewing the full flow helps you describe the correct order of actions and use the labels that users actually see. CapturedFlows support Source and Product Intelligence work by giving you a focused view of a journey before you create or update documentation. You can use the flow alongside your project’s documents, source context, and review process. > 📷 _Screenshot pending: The CapturedFlows area showing a selected product journey and its recorded steps._ ## Prerequisites Before you begin, make sure that: - You have access to the relevant project in Atloria. - A product flow has been captured for the journey you want to document. - You know which audience and documentation type the journey supports, such as **User Guides**. - You have permission to view project documentation and participate in review activities. - You have identified whether you are reviewing an existing document or preparing a new one. ## Step-by-Step Instructions 1. Open the project that contains the product journey you want to document. 2. Select **Loop Flows** to open the area where captured product journeys are available. 3. Select the captured flow that matches the user journey you need to review. 4. Review the first screen in the flow to understand where the user begins the journey. 5. Move through each recorded interaction in sequence to identify what the user selects, enters, or confirms. 6. Record the visible screen name, field name, and button label for each interaction you plan to describe. 7. Note any navigation actions that move the user to another screen, such as selecting **Documents** or **User Guides**. 8. Identify the outcome of the flow, such as reaching **Review & Publish**, opening **Preview**, or choosing **Export Documentation**. 9. Select **View Source** when you need additional context for a screen or interaction. 10. Use the **Source** view to confirm terminology and relationships that affect the journey you are documenting. 11. Return to the flow and compare the source context with the visible user experience. 12. Open **Documents** when you are ready to locate the documentation that describes the journey. 13. Enter keywords in **Search documents...** to find an existing page for the captured flow. 14. Select the relevant document from the search results. 15. Select **Preview** to check how the documented steps will appear to readers. 16. Select **Review & Publish** when the documentation is ready for the project review process. > 📷 _Screenshot pending: A captured flow showing sequential user interactions and the selected step’s screen details._ ## Tips and Best Practices - Review the flow in its recorded order. A user journey can depend on earlier actions, and documenting steps out of sequence can cause readers to miss required information. - Use the labels shown in the captured screens. For example, write **Search documents...**, **Review & Publish**, and **Export Documentation** exactly as users see them. - Document one user action per numbered instruction. If a user must select a button and then complete a field, make those separate steps. - Use the captured flow to distinguish navigation from completion. Selecting **Preview** lets users inspect documentation, while **Review & Publish** moves it into the review and publishing process. - Check source context when a screen’s purpose is unclear, but keep the finished User Guide focused on what users see and do. - Use **Back to Review** when you need to return from a detailed review view to the broader review process. - If a captured journey includes a documentation task, verify that the final instructions match the relevant document audience, such as **User Guides**. ## Related Pages - [Working with Documents](#) - [Creating a New Document](#) - [Searching Documentation](#) - [Reviewing and Publishing Documentation](#) - [Previewing and Exporting Documentation](#) - [Using Source Context for Product Intelligence](#) ## Troubleshooting ### You cannot find the flow you need Return to the project and select **Loop Flows** again. Confirm that you are viewing the correct project and that a flow has been captured for the journey you want to document. If no matching flow is available, request that the journey be captured before documenting it. ### The screen labels do not match an existing document Use the captured flow as the primary reference for what users see. Update the document to use the current visible labels, then select **Preview** to verify the revised instructions. ### You are unsure whether a document is ready to publish Review the complete captured journey, confirm that every user action is represented in the correct order, and verify the result of the final action. When the page is complete, select **Review & Publish** rather than assuming that previewing the page publishes it.