> 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/report-subscriptions.md).

# Report subscriptions

Have a report generated and delivered to you automatically on a schedule.

A **subscription** runs a report on a schedule and delivers it to you — so a monthly access report arrives without anyone remembering to produce it.

Open **Report Subscriptions** from the reports area.

## Creating a subscription

{% stepper %}
{% step %}
**Choose the report.**
{% endstep %}

{% step %}
**Set its parameters.**

The same filters you'd use when running it by hand — date range, department, scope. Each parameter needs a name and a value; if one is left blank you're told *"Report Parameter Value is not set"*.
{% endstep %}

{% step %}
**Choose the delivery method.**

How it reaches you — commonly email. If you skip this you see *"Delivery Method is not selected"*.
{% endstep %}

{% step %}
**Choose the audience.**

Who receives it: you, a group of people, a distribution list. Required — *"Delivery Audience is not selected"* if omitted.
{% endstep %}

{% step %}
**Choose the format.**

Spreadsheet, document, or another supported format. Required — *"Delivery Format is not selected"* if omitted.
{% endstep %}

{% step %}
**Set the schedule and save.**

How often it runs — daily, weekly, monthly. You see *"Report Subscription was saved successfully"*.
{% endstep %}
{% endstepper %}

## Testing before you rely on it

Use the test option to run the subscription once, immediately. You see *"Report Subscription Test successfully started"*, and the report is delivered as if the schedule had fired.

This is worth doing every time. It confirms three things at once: the parameters return the data you expected, the format is readable, and delivery actually reaches the audience. Finding out a month later that a subscription has been sending empty spreadsheets is a familiar and avoidable annoyance.

If the test won't start you see *"Report Subscription Test failed to start"* — contact your help desk.

## Changing or removing one

Edit a subscription to change its parameters, schedule, recipients, or format. Delete it when it is no longer needed — you see *"Report Subscription was deleted successfully"*.

{% hint style="info" %}
Review your subscriptions occasionally. Scheduled reports have a way of outliving their purpose: they keep arriving, everyone stops reading them, and sensitive access data circulates by email for no reason. If you no longer read it, delete it.
{% endhint %}

## Choosing a sensible schedule

* **Match the rhythm of the decision.** A report you act on monthly should arrive monthly, not daily.
* **Time it for when you'll read it.** A Monday-morning report gets read; a Friday-evening one doesn't.
* **Send it to a role, not just a person**, where your organization supports that — otherwise the report stops being useful the moment that person changes job.


---

# 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/report-subscriptions.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.