> For the complete documentation index, see [llms.txt](https://lern.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lern.sunbird.org/use/developer-guide/user-and-org-service/reports.md). # Reports There are two reports which comes under ‘MANAGE’ page in Sunbird Ed for 'ORG\_ADMIN' role. There reports are fetched from azure blob and details are displayed. Also allows to download in .csv format. UserOrg service jobs include: * State Admin Geo Report * State Admin Report or User Consent Report * User Cache Indexer Job #### Configuration and setup: These can be configured as cron jobs. \#Ansible: sunbirdstaging-admin-user-reports-3AMIST\ 30 21 \* \* \* /mount/data/analytics/scripts/run-job.sh admin-user-reports\ \#Ansible: sunbirdstaging-admin-user-reports-2PMIST\ 30 8 \* \* \* /mount/data/analytics/scripts/run-job.sh admin-user-reports\ \#Ansible: sunbirdstaging-admin-geo-reports-3PMIST\ 30 9 \* \* \* /mount/data/analytics/scripts/run-job.sh admin-geo-reports\ \#Ansible: sunbirdstaging-admin-geo-reports-4AMIST\ 30 22 \* \* \* /mount/data/analytics/scripts/run-job.sh admin-geo-reports Also can be run explicitly by using below jenkins job : Deploy/DataPipeline/AnalyticsReplayJobs set Job\_type : run-job set job\_id : admin-user-reports → for running User-Consent report admin-geo-reports → for running Geo-report --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://lern.sunbird.org/use/developer-guide/user-and-org-service/reports.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.