Make a status page private
Choose between a public status page and a password-protected one in Servor, and learn how to set and share a password for internal or staging pages.
Not every status page is meant for the whole internet. Servor lets you keep a page public for your customers, or lock it behind a password for internal teams, staging environments, or clients under NDA. This guide shows you the difference and how to switch.
Public vs password-protected
| Visibility | Who can see it | Good for |
|---|---|---|
| Public | Anyone with the link | Customer-facing status, badges, subscribers |
| Password-protected | Anyone with the link and the password | Internal dashboards, staging, private clients |
A public page is indexable and shareable — the normal choice for a customer status page. A password-protected page shows a password prompt before revealing anything, so only people you've given the password to can read the status, components and incident history.
Set a password
Open your status page settings
Go to Status pages in Servor, open the page, and find the Visibility setting.
Switch to password-protected
Change the visibility from Public to Password-protected.
Set a password
Enter the password visitors will need. Choose something you can share safely with the people who should have access.
Save
Save the change. The page now shows a password prompt to anyone who opens it.
Share the password out of band
Send the password through a channel your team already trusts — a password manager, an internal wiki, or a direct message — rather than in the same email as the link.
Switching back to public
You can flip a page back to public at any time from the same Visibility setting. The moment you do, the password prompt disappears and anyone with the link can read the page again. Switching visibility doesn't delete your components, incidents or history — it only changes who can reach the page.
Password protection is not per-user
A password-protected page uses one shared password, not individual logins. If you need to revoke access for one person, change the password and re-share it with everyone who should keep access.
What about subscribers and badges?
- Subscribers work best on public pages, since visitors need to reach the page to subscribe. On a password-protected page, only people with the password can subscribe.
- The status badge is designed for public pages — embed it where you want anyone to see live status at a glance.