# Configure Reporting Exports Configure reporting exports to share operational analytics outside Atloria in a consistent format. This page explains how to prepare your reporting view and export available data for documentation, analysis, or downstream reporting processes. ## Overview Reporting exports let you take the information displayed in your analytics area and create a file that can be reviewed, stored, or used in another reporting tool. Depending on the export option available on your screen, you can export data as a CSV file or a JSON file. Use exports when you need to provide operational reporting to stakeholders, retain a reporting snapshot, analyze data in a spreadsheet, or connect exported information to another internal process. CSV exports are generally best for spreadsheet-based review, while JSON exports are useful when a technical team needs structured data for another system. Before exporting, review the analytics information currently shown in Atloria. For example, your reporting view may include operational indicators such as **Compounding operational risks**, **✅ Security Best Practices Implemented**, or **Documentation Analytics**. Exporting after you have reviewed the displayed information helps ensure that the resulting file supports the report’s intended purpose. > 📷 _Screenshot pending: Analytics reporting view showing the available Export actions._ ## Prerequisites Before you begin, make sure that you have: - Access to the project’s Analytics area. - Permission to view the reporting information you intend to export. - A selected project with analytics data available. - A clear understanding of the audience for the export, such as operations leaders, auditors, or a documentation team. - A spreadsheet application for reviewing CSV files, if needed. - A secure storage location for exported files, especially when reports contain operational or security-related information. ## Step-by-Step Instructions 1. Open the project for which you want to prepare a reporting export. 2. Open the project’s **Analytics** area. 3. Review the reporting cards and operational information shown on the page. 4. Identify the information you need to include in your operational report. 5. Select **Configure →** if the Analytics area displays this action. 6. Review the available configuration options before continuing with the export. 7. Save or apply any available reporting configuration changes. 8. Confirm that the reporting view shows the information you expect to export. 9. Select **Export CSV** to download the displayed reporting data in CSV format. 10. Select **📄 Export CSV** if this is the CSV export action shown in your reporting section. 11. Select **📄 Export JSON** when you need the reporting data in JSON format. 12. Select **Export Documentation** when you need an export intended for documentation reporting. 13. Select **Export** when the screen provides a general export action rather than a format-specific button. 14. Save the downloaded file in your organization’s approved reporting location. 15. Open the exported file to verify that it contains the expected operational reporting information. > 📷 _Screenshot pending: Export actions showing CSV, JSON, documentation, or general Export options._ 16. Name the saved file according to your organization’s reporting convention. 17. Share the completed export only with the approved recipients for the report. 18. Record the export date and reporting purpose in your team’s reporting process. If the screen shows **2. Configured**, treat it as an on-screen indication that configuration is present or has reached that stage. Review the displayed reporting setup before exporting so that you do not distribute an outdated or incomplete report. ## Tips and Best Practices - Use **Export CSV** when recipients need to sort, filter, or review reporting data in a spreadsheet. - Use **📄 Export JSON** when another process requires structured data rather than a tabular report. - Use **Export Documentation** for reporting that supports documentation review or documentation-related analytics. - Review operational indicators before exporting. Items such as **Compounding operational risks** may require additional explanation when shared with leadership or risk owners. - Treat security-related reporting carefully. If the analytics view includes **✅ Security Best Practices Implemented**, confirm that the exported file is shared according to your organization’s security reporting procedures. - Export only after confirming that the analytics view reflects the project and reporting period you intend to report on. - Store exports in an approved location rather than leaving downloaded files in an unsecured local folder. - Use a consistent file name that includes the project, reporting period, and export format. For example: `ProjectName_Analytics_2026-07_CSV`. - If you export regularly, establish a repeatable schedule so stakeholders receive reports at predictable intervals. - Re-open each exported file before distribution. This simple check helps you catch an incorrect project selection or an unexpected export format. ## Related Pages - [View Project Analytics](#) - [Review Documentation Analytics](#) - [Manage Operational Risk Reporting](#) - [Configure CI/CD](#) - [Set Project Access and Permissions](#) ## Troubleshooting ### The export action is not available Confirm that you are viewing the correct project’s **Analytics** area. If **Export CSV**, **📄 Export CSV**, **📄 Export JSON**, **Export Documentation**, or **Export** does not appear, your access level may not allow exports, or that reporting view may not offer the selected format. Contact your Atloria administrator for access guidance. ### The exported file does not contain the information you expected Return to the Analytics area and review the reporting cards before exporting again. Confirm that you are in the intended project and that the visible analytics information includes the operational indicators you need. If available, select **Configure →** and verify the reporting configuration before creating a new export. ### I am not sure which export format to use Choose **Export CSV** for spreadsheet-based reporting and **📄 Export JSON** for structured data use. Choose **Export Documentation** when the report is intended to support documentation review. If your team has a required reporting procedure, follow that procedure before sharing the file.