> 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/administration-guide/reference/shipped-reports.md).

# Shipped reports

The reports OpenIAM ships, the reporting engine behind them, and where the definitions live.

## What this is, and when you need it

A shipped report is a question OpenIAM can already answer without anyone writing a query: who holds what, what changed, what failed, who has not signed in. Check this list before commissioning a new report — and note that a report is a resource, so a colleague who cannot see one is usually missing a grant rather than a definition.

OpenIAM ships **25** report definitions as `REPORT_INFO` rows. Reporting is Eclipse BIRT: each report pairs a Groovy data source with a `.rptdesign` layout, rendered by the `openiam-reportviewer` service. Which export formats the viewer offers is fixed by that service's own configuration at startup rather than by anything on **Administration → System Configuration**; if a format you expect is missing from the export menu, that is a deployment question, not a report question — see the [Installation Guide](/installation/installation.md).

{% hint style="info" %}
Since 2026.10.1 OpenIAM also has a **report builder** with its own Data Catalog, wizard, scheduler and Download center. It is a separate feature from the reports on this page: see the [Report builder](/administration-guide/reports.md) section, and [System templates](/administration-guide/reports/system-templates.md) for the report definitions it ships.
{% endhint %}

| Report ID                        | Report name                      |
| -------------------------------- | -------------------------------- |
| `118`                            | `ACCESS_CERTIFICATION_REPORT`    |
| `121`                            | `AUDIT_REPORT`                   |
| `105`                            | `EMPLOYEE_CERT_REPORT`           |
| `ENTITLEMENTS_MEMBERSHIP_REPORT` | `ENTITLEMENTS_MEMBERSHIP_REPORT` |
| `ENTITLEMENTS_REPORT`            | `ENTITLEMENTS_REPORT`            |
| `122`                            | `GENERIC_REQUEST_REPORT`         |
| `113`                            | `GROUP_AUDIT_REPORT`             |
| `111`                            | `GROUP_REPORT`                   |
| `117`                            | `LAST_LOGIN_REPORT`              |
| `120`                            | `ORPHANED_USER_ACCOUNTS`         |
| `110`                            | `PASSWORD_CHANGES_REPORT`        |
| `PR_FAIL_REP`                    | `PROVISION_FAILURE_REPORT`       |
| `103`                            | `RECONCILIATION_REPORT`          |
| `115`                            | `REQUEST_REPORT`                 |
| `106`                            | `RESOURCE_CERT_REPORT`           |
| `116`                            | `RESOURCE_USAGE_REPORT`          |
| `114`                            | `ROLE_AUDIT_REPORT`              |
| `104`                            | `SYNCHRONIZATION_REPORT`         |
| `TERMINATED_USER_REPORT`         | `TERMINATED_USER_REPORT`         |
| `107`                            | `TERMINATING_ACCOUNTS`           |
| `108`                            | `TOP_ACTIVE_USERS`               |
| `109`                            | `USER_ACCESS_REPORT`             |
| `119`                            | `USER_LIFE_CYCLE_ACTIVITIES`     |
| `101`                            | `USER_REPORT`                    |
| `112`                            | `WORKFLOW_STATUS_REPORT`         |

## Report parameters and access

A report is a resource. A user who cannot see a report either lacks the entitlement or lacks the menu item — check both. Report parameters are declared in `REPORT_PARAM_META`; a report that returns no rows for an administrator who expects data is more often a parameter default than a permission problem.

{% hint style="info" %}
`LAST_LOGIN_REPORT` reflects what the login modules record, not every authentication path. If a federated or delegated sign-in does not appear, confirm which module handled it before treating the report as wrong.
{% endhint %}

*Applies to OpenIAM 2026.8.1. Last reviewed 7 August 2026.*


---

# 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/administration-guide/reference/shipped-reports.md?ask=<question>&goal=<user_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.