> ## Documentation Index
> Fetch the complete documentation index at: https://docs.knoxcall.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Status Page

> Let the operator console post incidents to the status-page Worker — generate a shared admin token, set it on the Worker, and enter the same value here with the Worker URL.

# Status Page

The public status page is a Cloudflare Worker. This card holds the **shared admin token** the console presents when it posts incidents and updates to it. It is not a vendor credential — it is a value you generate and configure on both sides.

**Scope: Global defaults** only — a platform operator feature.

## 1. Generate and deploy the token

1. Generate a high-entropy token:

```bash theme={"dark"}
openssl rand -base64 32
```

2. Set it on the Worker as its admin-token secret (`wrangler secret put …` for the Worker's admin-token binding) and deploy the Worker.

## 2. Enter it in KnoxCall

**Settings → Integrations → Global defaults → Status page** → *Configure*:

| Field                       | Value                                                |
| --------------------------- | ---------------------------------------------------- |
| **Worker admin token**      | The **same** value you set on the Worker             |
| **Worker URL** *(optional)* | Only if the Worker is not at the default status host |

**Save credentials.**

## 3. Verify

Open the console's status admin page. A failed load, or a `401` from the Worker, means the two values have diverged.

## Things that bite

* **Rotation is two-sided.** Change it on the Worker and here, or incident posting breaks. Save the new value here first if the Worker still accepts the old one during a rollout.
* **Environment fallback**: `STATUS_ADMIN_TOKEN` is used when no row is stored.
* **The token is full control of the status page.** There is no scoping.