Documentation

Admin Guide

Manage your workspace — members, checkers, status pages, and integrations.

Dashboard

Admins have the same day-to-day monitoring view as regular users, including alert pinning, personal row ordering, and workspace switching.

For the user-facing dashboard workflow, see the User Guide dashboard section.

Profile

Admin profile settings match the user experience: update first name, last name, and password from Profile. Email addresses stay fixed on the account.

For the standard profile flow, see the User Guide profile section.

Targets

Admins can view and manage all targets in the workspace and have the full user target-detail workflow, including immediate checks, signal review, and history access.

For the shared target-management UI, start with the User Guide targets section.

Members

The Members page lists every workspace user with their name, email, role, join date, and available actions. Admins can change a member’s role or remove them from the workspace.

Removing a member also clears any per-target visibility rules saved for that user. PulseQuay enforces that at least one admin must remain, so you cannot remove yourself if you are the sole admin.

Invitations

Use the Invite member form on the Members page to send an invitation by email. New PulseQuay users receive a registration link; users with an existing account receive an accept or decline link.

Pending invitations appear in the Pending Invitations section and can be cancelled at any time. Invitations expire after 72 hours; if one expires, send a fresh invite instead of waiting on the original link.

Checkers

Multiple checkers give you more realistic visibility across regions and networks. A checker inside the same private network as a service can detect outages that a public checker would never see.

Pull checkers are reached by the API on a schedule and must be network-reachable. Deploy them with Docker using the Pull Checker Guide →.

Push checkers poll the API for config and push their results back, so they work without inbound access behind firewalls or NAT. Deploy them with Docker using the Push Checker Guide →.

To register a checker, open the Checkers page, choose the checker type, enter the name and either the URL for pull mode or the miss threshold for push mode, save the form, and copy the API key while it is shown.

The checkers table includes the type badge PULL/PUSH, status, last heartbeat or config request, and the assigned target count. Pull checkers are marked down when the API’s /healthz probe fails. Push checkers are marked down if no heartbeat arrives inside the configured miss-threshold window. Assign a checker from the target edit form’s checker dropdown.

Status Pages

Status pages use a workspace slug plus a page slug in the public URL: /statuspage/<workspace-slug>/<page-slug>. The workspace slug defaults to the workspace name lowercased with spaces replaced by hyphens, but you can edit it in Status Pages settings.

Create a page with New page, give it a name, optionally set a page slug, and add targets from the dropdown. Leaving the slug blank makes it the default page for the workspace.

Use the Published toggle to control whether the page is live. Published rows show a link icon that opens the public URL in a new tab. The pages table lists name, slug, published state, and target count.

Clients

Create client labels from the Clients page and assign them to targets in the target edit form. You can rename or delete client entries without affecting the targets themselves. They are intended for customer-level or project-level organisation.

Settings

Workspace settings start with the general workspace name and extend into integrations available on Starter and higher plans.

  • Discord: paste a Discord incoming webhook URL to deliver alerts as Discord messages. Setup reference: Discord webhook docs →
  • Slack: paste a Slack incoming webhook URL to deliver alerts into Slack. Setup reference: Slack incoming webhooks →
  • Telegram: paste a Telegram bot token. Each target rule sets the destination chat ID. Setup reference: BotFather guide →
  • Webhook: configure per-target outbound HTTP calls with URL, method, optional bearer token, optional Go text/template payload, selected alert types, and a TLS verify toggle.