> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/incidents-and-status-pages/status-pages/audience-specific-status-page.md).

# Audience-specific status page

Create audience‑specific status pages in ilert tailored to different stakeholder groups with custom branding and messaging.

## Overview

An **audience-specific status page** is a private page accessible only to authenticated ilert users or stakeholder accounts. It dynamically presents services and metrics tailored to each user's team assignments, ensuring that everyone sees only the information relevant to them.

{% hint style="info" %}
An audience-specific page doesn't support authentication via IP or email whitelists.
{% endhint %}

### Use cases

Audience-specific status pages are ideal for providing tailored content to different user groups. Below are key scenarios where such pages are beneficial:

* **Internal employee status page:** Allow internal employees to view the status of services they have permission to access. This ensures that sensitive information remains secure while keeping your team informed about the services that matter to them.
* **Customer-specific status page:** Show status updates to customers based on the services they subscribe to. This personalized approach enhances customer satisfaction by providing relevant information.
* **Single-Tenant Hosting:** If you offer dedicated instances to each of your customers, you can display status information specific to each customer. This allows for a customized experience that reflects the unique environment of each client.

### Benefits

Creating audience-specific status pages enhances both security and usability by allowing you to:

* **Customize visibility**: Select which services and metrics are visible to specific users or groups. This ensures that users only see information relevant to them.
* **Enhance security**: Restrict access to sensitive information by making the status page private and accessible only to authenticated users.
* **Improve user experience**: Provide users with a tailored view of services and metrics, improving the relevance and usefulness of the information they receive.

## Managing the audience of your status page

After creating an audience-specific status page, you can manage which services and metrics are visible to different audiences (teams) in your organization. Follow these steps to configure your audience settings:

1. **Add everything the page could ever show.** On the page's **Services** and **Metrics** tabs, add every service and metric you might want any audience to see. This is the superset; the Audience tab narrows it.
2. **Decide who sees what.** Switch to the **Audience** tab. An audience is a team, and any team that owns one or more of the services or metrics from step 1 appears here with those items listed.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fgit-blob-ac01fa1ea8890d832065767b80d788aeef27aea9%2Fstatus-page-audience-tab.png?alt=media" alt="The Audience tab of an ilert status page, with an Add teams button and one team block showing an Enable notifications toggle, an Add users to this team link, and a per-service visibility toggle."><figcaption><p>One block per team, one toggle per service.</p></figcaption></figure>

* **The toggle beside each item** decides whether that audience sees it. Turning it on also adds the item to the team.
* **Enable notifications** decides whether that audience is notified about updates, rather than only seeing them when they visit.
* **Add users to this team** puts people into the audience — and, since an audience *is* a team, into the ilert team as well.

## FAQ

### Do I need to purchase full user licenses so that users can view an audience-specific status page?

No. A [Viewer](/users-and-access-management/user-roles-and-permissions.md#viewer) license is sufficient, and Viewer licenses are free and unlimited.

### How can I create a new audience?

Audiences are defined based on your team structure in ilert. You can create as many teams as you need, either by reusing your existing team structure or by creating new teams specifically for your audience-specific status pages.

To add a team as an audience:

1. **Open the Audience tab** in your status page settings.
2. **Click Add teams.**
3. **Select or Create a Team:**
   * **Select an Existing Team:** Choose from the list of existing teams.
   * **Create a New Team:** If you need a new audience, you can create a new team directly from this interface.
4. **Configure Visibility:** After adding the team, you can manage which services and metrics are visible to this audience by toggling the switches next to each item.

By organizing your audiences through teams, you can tailor the content of your status pages to specific groups within your organization or customer base, ensuring that each audience sees only the information relevant to them.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ilert.com/incidents-and-status-pages/status-pages/audience-specific-status-page.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
