# Best Practices

#### Define the audience first

Before creating a status page, decide:

* Is it public?
* Is it internal?
* Is it for partners?

Audience defines content and tone.

#### Public vs Private status pages

Public status pages should:

* Include only customer facing services
* Be updated during incidents
* Build trust through transparency

Private status pages can:

* Include technical detail
* Track internal incidents
* Be protected by password, IP or SSO

Do not mix internal and customer facing information.

#### One board, one status page

Each board maps to one status page.

If you need different audiences, you likely need different boards.