SaaS

Statuspage

Statuspage is Atlassian's hosted status page product. Connecting it lets Ploy see two kinds of people in your Statuspage organisation:

  • Team members: the staff who log in to post incidents and manage your pages.

  • Subscribers: everyone who asked to be notified about incidents on each of your status pages, by email or SMS.

Ploy scans both every hour, shows each subscription as access to that status page, and can remove a person's subscriptions when they leave.

This integration is in beta

Statuspage is a beta integration. When you connect it, the first step of setup asks you to accept that Ploy may send redacted error data from Statuspage to our monitoring while the integration is in beta. "Redacted" means any personal data or secrets in an error response are masked before it leaves Ploy; only the shape of the error is kept so we can fix problems quickly. SMS subscriptions in particular were built from Statuspage's documentation rather than a paid test account, so please tell us if anything about them looks wrong.

Before you start

You need to be an account owner in Statuspage. Only owners can create API keys.

Step 1: Create an API key

  1. Sign in to Statuspage at https://manage.statuspage.io.

  2. Click your avatar in the bottom left, then API info.

  3. Click Create key. Give it a name and choose an expiry (1 to 365 days).

  4. Copy the key straight away. Statuspage never shows it again.

The key expires after the period you chose, so make a note to reconnect Ploy with a new key before then.

Step 2: Find your Organization ID

Statuspage does not label the Organization ID anywhere on screen. It is in the address bar of the API info page:

https://manage.statuspage.io/organizations/<Organization ID>/api-info

Copy the part between organizations/ and /api-info. It is a short code such as 6hy44bz8lk85.

Do not use a Page ID from the "Page IDs" section of that screen. Page IDs identify individual status pages and are a different thing.

Step 3: Connect in Ploy

  1. In Ploy, go to Integrations, find Statuspage and click Connect.

  2. Accept the beta notice.

  3. Enter the Organization ID and paste the API key.

  4. Click Test connection, then save.

If the test fails with a message about the API key, create a new key as an account owner and try again. If it fails with a message about the Organization ID, check you copied it from the address bar and not from the Page IDs list.

What Ploy shows

  • Each status page appears as a resource of type site.

  • Each team member appears as an identity with access to the Statuspage app.

  • Each active email or SMS subscriber appears as an identity with access to the status page they subscribed to. An email subscriber is matched to the employee with that email address. An SMS subscriber is matched to the employee whose mobile number it is, using the mobile numbers your HR integration provides. If no employee has that number, the subscriber appears without an owner and you can assign one by hand.

  • Subscriptions that are unconfirmed or quarantined are not shown, because Statuspage sends them nothing.

Removing people

  • Remove user (for example from an offboarding flow) removes every email and SMS subscription that person holds on every page, matched by their email address and mobile number. For a team member it first removes their subscriptions, then asks Statuspage to remove the team member; organisations managed by Atlassian refuse that last step, so remove team members in Atlassian admin instead.

  • On a status page's resource page, Remove access unsubscribes one person from that page, and Grant access subscribes an email address (Statuspage sends them a confirmation email).

Limits

  • Statuspage exposes no last-login, MFA or audit data, so Ploy cannot show them.

  • Team member roles per page are not scanned yet.

  • Page access users on audience-specific pages are not scanned yet.

Was this helpful?
Was this helpful?