> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/end-user-guide-for-selfservice/reports.md). # Reports Run the reports available to you and read the results. SelfService can give you reports about identity and access — who has what, what was requested, what changed. Which reports you can see depends on your role: most people see none, managers see reports about their team, and people with a governance role see more. Open **Reports** from **Administration → Reports**. If you do not see the menu, no reports have been made available to you. ## Running a report {% stepper %} {% step %} **Choose the report.** Reports are named after what they answer — user access, entitlements, request activity, audit history. {% endstep %} {% step %} **Set the parameters.** Most reports ask you to narrow the scope: a date range, a department, a particular person or application. Keep it narrow — a report across everything is slow to produce and hard to read. {% endstep %} {% step %} **Generate it.** Results are produced and delivered in the format your organization has configured — commonly a spreadsheet. {% endstep %} {% endstepper %} ## What reports are good for * **Preparing for an access review** — see what your team holds before the campaign starts, so the review itself is quick. * **Answering "who has access to this?"** — for an audit question, or before changing a system. * **Checking a change took effect** — after a transfer or a leaver, confirm access actually moved. * **Spotting accumulation** — people holding far more than their peers usually signals access that was never cleaned up. ## Reading them sensibly * **A report is a snapshot**, accurate at the moment it ran. Access changes continuously; a week-old report is history, not current state. * **Empty isn't necessarily broken.** It often means the filters were too narrow — or genuinely that nothing matched. * **Large reports take time.** Generation runs in the background; you may be notified when it's ready rather than waiting on screen. ## Getting a report regularly If you need the same report every week or month, subscribe to it rather than running it by hand — see [Report subscriptions](/end-user-guide-for-selfservice/reports/report-subscriptions.md). {% hint style="warning" %} Reports about people's access are sensitive. They show who can reach what, which is exactly what someone planning misuse would want. Store them carefully, share them only with people who need them, and delete old copies. {% endhint %} --- # 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://docs.openiam.com/end-user-guide-for-selfservice/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.