> For the complete documentation index, see [llms.txt](https://docs.spike.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spike.sh/status-pages/manage-your-subscribers.md).

# Manage your subscribers

Visitors subscribe directly from your status page using email, RSS/Atom, Slack, or Microsoft Teams. From your settings, you can control who can subscribe, restrict by domain, and import subscribers in bulk.

## How to subscribe

{% tabs %}
{% tab title="Email" %}

<figure><img src="/files/XUDCVAcwceEPe8TL9QV4" alt="Email subscription option on Spike status page"><figcaption></figcaption></figure>
{% endtab %}

{% tab title="RSS / Atom" %}

<figure><img src="/files/7s96Exunku3ri9rxcQsj" alt="RSS/Atom subscription option on Spike status page"><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Slack" %}

<figure><img src="/files/b817AMrRq0TecrMr9qFY" alt="Slack subscription option on Spike status page"><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Microsoft Teams" %}

<figure><img src="/files/3wy0K8zAJw5IBFs0ZbS6" alt="Microsoft Teams subscription option on Spike status page"><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}

### Email subscription

Email is the most common subscription method. Subscribers do not receive a confirmation email after subscribing. The subscribe button appears on both public and private status pages. Email notifications follow your status page theme. Set up branding [under Themes](https://statuspage.spike.sh/themes).

{% hint style="info" %}
Subscribers on private status pages must have a Spike account.
{% endhint %}

### RSS subscription

Subscribers can use an RSS or Atom feed to receive updates. Private status page feed URLs include a unique token.

Use the RSS feed to post status updates to Slack or Microsoft Teams channels, or to automate updates across other systems.

## Configure subscriber control

Open **Security & Access** in your status page settings ([link](https://statuspage.spike.sh/configure/security-access)) to control who can subscribe:

* **Allow new subscribers**: enabled by default
* **Restrict by email domain**: only specified domains can subscribe (add subdomains separately)
* **Disable unsubscribe**: subscribers cannot remove themselves

| Allow new subscribers | Subscribers with domains | Who can subscribe?           |
| --------------------- | ------------------------ | ---------------------------- |
| Enabled               | Disabled                 | Anyone                       |
| Enabled               | Enabled                  | Specified email domains only |
| Disabled              | Automatically disabled   | No one                       |

## Import subscribers

Open the **Subscribers** section from the sidebar ([link](https://statuspage.spike.sh/subscribers)) to see all active subscribers, delete individual subscribers, or import new ones via CSV. The CSV must include an **Email** header. No other fields are processed.

{% hint style="info" %}
Subscribers are scoped to each status page and cannot be shared across pages. To add the same subscribers to multiple pages, upload the CSV to each one.
{% endhint %}

## Notify subscribers

When creating incidents or posting updates, enable the notify option to send email and RSS updates to subscribers. This option is enabled by default.


---

# 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:

```
GET https://docs.spike.sh/status-pages/manage-your-subscribers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.