Status Pages and the Builder
Open Status pages in the Probed dashboard, select your page, and choose Builder. Public pages open in the Builder by default. Protected pages use Components and Settings; their live Builder preview is not currently available.
Build the page
The Builder edits a draft and shows a private preview beside it. On a narrow screen, switch between Edit and Preview.
- Monitors: add an existing workspace monitor or a static component, arrange components into groups, and set their names and descriptions. A monitor-linked component follows that monitor; use reports to communicate changes for manually managed services. Create a monitor first if the picker is empty. The grouped component picker currently disables Add Third-Party Component.
- Components: show or hide page features, including subscriber updates, recent events, Details, Latency, and footer controls. These switches control visibility; they do not freely reposition those features. Removing Probed branding requires White Label.
- Page content: edit the title, description, logo, homepage link, and contact link.
- Display: choose the page layout, width, history source and style, uptime display, monitor presentation, custom links, and related pages. The Status timeline, Compact status, and Technical overview presets change presentation without replacing the selected monitors, links, or time window.
- Color scheme: choose a preset and edit the page's light and dark colors where your plan permits it. A preview color override lets you inspect light or dark without changing the saved page's color mode.
- Custom CSS: apply page styles where your plan permits it. This requires White Label. Remote
@importis not supported; use@font-facewith an HTTPS URL for fonts.
A component's status, a monitor's measured health, and a report's message are different things. Use status reports for incidents and maintenance windows for planned work; changing the page layout does not change a monitor's checks.
Preview and publish changes
Show example adds illustrative data to the private preview so you can try presentation options. It does not publish fake monitor results. The preview's status banner and events reflect saved components; draft names or layout changes do not create live incidents.
Visitors continue to see the saved version until you click Save changes. Review the preview, save, then open Saved page to check the public result. Discard returns unsaved edits to the saved version and leaves the public page unchanged.
If saving would remove components, the Builder asks for confirmation. Removal also unlinks those components from reports, maintenance windows, and subscriptions; check the listed components before choosing Remove and save.
Recover an interrupted edit
If data cannot be refreshed, retry before saving. An error loading the preview does not mean your changes were published.
If another editor saved the page first, the Builder reports a conflict and saves nothing from your draft. Keep editing to copy anything you need, or choose Reload saved version to load the new saved page and drop your local edits.
Draft backup belongs to the current browser session. It is not a published version or a shared team draft. If the Builder reports that backup is unavailable, preserve important edits before leaving. A conflicting saved page can offer Export draft before you discard its browser backup.
If saving succeeded but refreshing failed, reload the saved version before editing again. If the save outcome is uncertain, inspect Saved page before retrying.
Settings, audience, and automation
Use Settings for the page slug, domain, access, and other settings shown there. Review a public page without a dashboard session. For restricted pages, verify both allowed and denied visitor paths before sharing its address.
Subscriber messages and monitor alert channels serve different audiences. Review notification choices when publishing reports or maintenance updates; configure monitor alert channels separately under Notifications.
For agent-driven changes, use the dashboard's Connect via MCP setup and the Probed MCP guide. API integrations should follow the current API contract. Automation must read the saved configuration and use the corresponding operation's schema; the private browser preview is not a public editing API.