Outage AppOutage App
Sign InSign Up

Outage App User Guide

How to declare and track incidents, keep people informed, plan and approve changes, and automate the routine parts of your operations.

Getting started

5 minutes

Outage App is where your team records outages and planned maintenance, tells the right people about them, and plans and approves changes. Everything belongs to an organization (your company). People in one organization never see another's data.

Create your account and organization

  1. Choose Sign up. Enter your name, work email, a password (10 to 128 characters) and your company name.
  2. Open the confirmation email we send you and select the link. Your organization is created when you confirm, and you are signed in. Check your spam folder if it does not arrive within a few minutes. You can ask for another link from the sign-in page, one per minute.
  3. You become the organization's Owner. Next, add your sites, services and the people to notify under Recipients, then invite your colleagues.
If email is switched off for your deployment, the page says “Sandbox mode: no email was sent” and shows the link on screen instead. That only happens in test setups. Real deployments email you.

Signing in, and forgotten passwords

  • Sign in with your email and password. Your session ends when you sign out or when an administrator ends it.
  • Forgot password? on the sign-in page emails you a reset link. The reply is the same whether or not the address has an account, so nobody can use it to find out who is registered.
  • My account (click your name in the sidebar; every role can open it) shows where you are signed in and lets you sign out other devices. There you can also turn on the emailed sign-in code: after your password, a 6-digit code goes to your email address, and you can tick Remember this device to skip it on that browser for 30 days.

Joining an existing organization

Administrators invite people from Settings → Invitations. Open the link in your invitation email, set a password if you are new, and you join with the role you were invited with. The invitation only works for the email address it was sent to. If you belong to several organizations, switch between them from the menu in the top bar.

Roles & what you can do

Access

Each person has one role in each organization. The menu only shows the pages your role can use. If you open a page you cannot use, it says so.

RoleWhat it is forCan do
OwnerThe accountable person for the organization.Everything, including granting or removing the Owner role. An organization always keeps at least one Owner.
AdministratorRuns the workspace day to day.Everything except managing Owners: settings, people, integrations, automations, audit export.
Change managerReviews changes.Approve or reject changes, create and edit incidents and changes, send notices, read the activity log.
OperatorThe responder on the day.Create and update incidents and changes, send notices, manage recipients, sites and services.
ViewerStays informed.Read-only: incidents, changes, the calendar, automations and the people list.

Also a change manager. An Owner or Administrator can give an Operator or a Viewer a change manager's abilities (approving changes, planning changes, sending notices, reading the activity log) without changing their role: tick Also a change manager under Settings → Users & invitations, or when inviting them. It adds abilities and never takes any away, and it never includes settings, people or billing.

You can never give someone a role higher than your own, and only an Owner can grant or change the Owner role. Roles are fixed; custom roles are not available. Everyone with an account, whatever the role, counts as a billable user.

Permissions by role

Every action is checked on the server against this table on every request. It is read from the same table the server uses, so it is always current.

PermissionOwnerAdministratorChange managerOperatorViewer
Organization
See the organization, overview and usageAllowedAllowedAllowedAllowedAllowed
Change settings, branding and the company logo, and send a test emailAllowedAllowedNot allowedNot allowedNot allowed
See and change the plan, extra users, payment method and invoicesAllowedAllowedNot allowedNot allowedNot allowed
Download all organization data, and delete the organizationAllowedNot allowedNot allowedNot allowedNot allowed
People
See members and pending invitationsAllowedAllowedAllowedAllowedAllowed
Invite peopleAllowedAllowedNot allowedNot allowedNot allowed
Change members' rolesAllowedAllowedNot allowedNot allowedNot allowed
Remove membersAllowedAllowedNot allowedNot allowedNot allowed
Activity log
View the activity logAllowedAllowedAllowedNot allowedNot allowed
Download the activity log as a fileAllowedAllowedNot allowedNot allowedNot allowed
Incidents
See incidents, sites and servicesAllowedAllowedAllowedAllowedAllowed
Create and update incidents; manage sites and servicesAllowedAllowedAllowedAllowedNot allowed
Communications
Send notices; manage recipients, groups and templatesAllowedAllowedAllowedAllowedNot allowed
Changes
See changes and the calendarAllowedAllowedAllowedAllowedAllowed
Create and edit changesAllowedAllowedAllowedAllowedNot allowed
Approve or reject changes; see the approvals inboxAllowedAllowedAllowedNot allowedNot allowed
Automation
See workflows, validate and simulate themAllowedAllowedAllowedAllowedAllowed
Create and edit workflow draftsAllowedAllowedNot allowedNot allowedNot allowed
Publish, run, pause and cancel workflowsAllowedAllowedNot allowedNot allowedNot allowed
Create and manage inbound integrationsAllowedAllowedNot allowedNot allowedNot allowed

Incidents & maintenance

Operations

An incident is the record of something that is affecting people: either an outage that just happened, or maintenance you have planned. It holds the times, who is affected, the running timeline and who gets updates.

Declare an incident or schedule maintenance

  1. Open Incidents → New. Choose Unplanned outage (something broke) or Planned maintenance (work you scheduled).
  2. Give it a Title and an optional Summary, pick a severity, and choose the affected sites and services.
  3. Set the times. For an outage: Detected at (when someone noticed) and, if it began earlier, Impact began. For maintenance: Planned start. Add your best estimate of when service will be restored, or how long the work should take. You can revise it with every update.
  4. Choose who should hear about it (recipient groups and individual contacts). Leave Send the first notice now ticked to email them straight away, or untick it to save the incident quietly and notify later.
From an approved change: on the change page, Create planned incident makes the maintenance record for you (title, window, sites and services). The dialog also asks who to tell: choose recipient groups and people and leave Send the planned-maintenance notice now ticked, and the notice goes out as the incident is created. Choose nobody and nothing is sent.

Severity and status

SeverityUse it for
CriticalA major service is down or many people are blocked.
HighSerious disruption or a key function degraded.
MediumNoticeable problem with a workaround.
LowMinor issue affecting few people.
InfoHeads-up with no real impact.

An outage moves through Investigating → Identified → Monitoring → Resolved → Closed. Planned maintenance starts as Planned (it has not started yet) and can then move to any of those steps, for example Monitoring while the work is under way and Resolved (shown as “Mark complete”) when it is finished. Choose the next status on the incident page. Your administrator can require a note when you resolve or close (Settings → Policies). A closed incident is read-only.

Keep the timeline and the audience up to date

  • Update Incident on the incident page posts a note to the timeline. Pick a new status in the same step if it has changed.
  • Restoration ETA revises when you expect service back. Scope adds or removes affected sites and services. Edit details and Edit times correct the record.
  • The Notify switch emails the incident's audience about that update. It is off unless you turn it on, and it is disabled until you add recipients. Use Who gets updates to change the audience at any time. Changing only the audience never sends anything.
  • When you resolve an incident, the downtime is calculated for you from the start and end times.
Finding things: the search box in the top bar finds incidents, changes and automations by title. Press Enter to list every incident that matches.

Notifying people

Communication

Notices are the emails that tell people what is happening. You write and send them from the incident; the Notifications page is the log of everything sent and how each email fared.

Recipients, groups, sites and services

  • Recipients are the people who get notices: a name and an email address. They do not need an account. Groups bundle recipients (for example “Plant 1 managers”) so you can pick one name.
  • Sites (places) and services (systems) are the lists you choose from when you say what an incident or change affects. Add them on the Recipients page.
  • Each list on the Recipients page (people, groups, sites, services) has a search box and scrolls inside its own box, so long lists stay manageable.
  • Groups can mirror Microsoft Entra groups (Settings → Directory, see the Settings section). Those groups and their people are marked From Entra, are kept in step automatically, and cannot be edited by hand here.
  • Nobody gets the same notice twice. If you pick several groups and someone is in more than one (or you also pick them by name), they receive one email, matched by email address.
  • Sites, services, groups and recipients can all be edited or deleted there. Deleting asks you to confirm. A site or service that is still used by an incident or change cannot be deleted; the message tells you what uses it. Past records keep pointing at it.

Import many recipients from a CSV file

  1. On Recipients, find Import from CSV. Download the template if you want a starting point. The file needs a header row with email (required), name and groups (separate several groups with a semicolon).
  2. Choose your file. Before anything is saved, you see how many people will be added or updated, how many groups will be created, and which rows will be skipped and why.
  3. Choose Import to apply it. Skipped rows are left out; the rest are imported.

Importing only adds new people and updates names of existing ones (matched by email). It never deletes anyone and never removes anyone from a group. Each file can hold up to 2,000 rows.

Sending a notice

  • Turn on Notify when you create or update an incident. The default wording suits an initial notice, an update and a resolved notice.
  • Choose Preview email to see the exact wording, recipients and layout before anything is sent. You can replace the default wording. Placeholders such as {{incident_title}}, {{incident_number}}, {{incident_status}}, {{incident_estimated_end}}, {{sites}} and {{services}} fill in automatically.
  • A notice cannot go to more people than your organization's limit (Settings → Policies, up to 500). It is refused before anything is sent, never half-sent.

Is it really sent? Live and sandbox

Email is on for every organization. Notices go to the recipients you choose, so an organization that does not want email simply does not add recipients. Only a server with no email provider connected cannot send: there, notices are recorded but nothing is emailed, and each is labelled Sandbox. Outage App never shows a sandbox notice as delivered. If people say they got nothing, check this first.
Delivery statusWhat it means
In progressQueued or being handed to the email service.
AcceptedThe email service took it. This is not proof it reached the inbox.
DeliveredThe recipient's mail server confirmed it.
Bounced / BlockedThe address does not exist or the mail server refused it. Correct the address under Recipients.
Marked as spamThe recipient reported it. We stop emailing that address.
FailedWe could not hand it over. A failure for a bounced or blocked address is skipped on retry.

If some deliveries failed, the notice shows Retry failed deliveries. When we cannot tell whether an email went out (for example the connection dropped mid-send), we never resend by ourselves. You are asked to confirm, because the person may then get the same email twice.

Emails are plain, designed messages with your logo (Settings → Branding). They contain no tracking pixels or remote images.

Changes & approvals

Planned work

A change is a request to alter something in production, planned in advance, reviewed, and scheduled. The Calendar shows approved maintenance and active incidents together so you can spot clashes.

Request a change

  1. Open Changes → New. Give it a title and description and choose its type: Standard (pre-authorized, low risk), Normal (routine, normal review) or Emergency (urgent fix, expedited approval).
  2. Rate the risk: Low, Medium, High or Critical.
  3. Set the start time, end time and timezone, the affected sites and services, and a service impact summary.
  4. Write the implementation plan, how you will validate it, and the rollback plan. Reviewers decide on these.
  5. Choose Submit for approval. (If your organization does not require approval it reads Submit (auto-approve).)

Approving and rejecting

  • Everyone has an Approvals page, and it shows only what was sent to you: approvals an automation sent to you by name (whatever your role), and, for requests that name nobody and for change requests, those open to roles that can approve changes (Owners, Administrators, Change managers). Open a request, read exactly what is proposed, and Approve or Reject it with a reason. Owners and Administrators can always see and settle everything in their organization.
  • You are emailed. When a change is submitted, everyone who can approve changes (never the person who asked) gets an Approval needed email with a link to the Approvals page. An automation's approval step emails the people it names, or everyone who can approve changes when it names nobody. When a change is approved or rejected, the person who requested it is emailed the outcome. (Sandbox mode sends nothing and says so.)
  • The approval applies to the change as it was when you read it. If the requester edits the change afterwards, the old approval is no longer valid and the change must be reviewed again.
  • Your administrator can stop people approving their own requests, set how many days a request waits before it expires, and require approval for every change (Settings → Policies).

Carrying the change out

A change moves through Draft → Submitted → In review → Approved → Scheduled → Implementing → Verification → Completed. It can also end as Rejected, Canceled, Failed or Rolled back. After approval, use the Mark … buttons on the change page to move it along as the work progresses. Every step is recorded in the activity log.

Automations (workflows)

No code

An automation does routine work for you: when something happens, check a condition, wait, ask for approval, send a notice or update an incident. You build it by connecting steps on a canvas in Workflows. There is no code.

Build one

  1. Choose New workflow, or start from a template such as “notify immediately for a critical incident”.
  2. Add a trigger, then add steps and connect them. Select a step to fill in its settings.
  3. Use Checks to see problems, and Test to simulate a run with sample data. A test shows what would happen and sends nothing.
  4. Publish to make it live. Each publish is a numbered version, and you can see earlier versions. Use Run history to see what each run did, step by step.
Step typeStepWhat it does
TriggerIncident eventStarts when an incident opens or changes status, optionally only for chosen severities.
TriggerChange eventStarts when a change is approved, rejected or changes status, optionally filtered by type and risk.
TriggerWebhook eventStarts when a matching event arrives from one of your integrations.
TriggerScheduleStarts every N minutes, daily, or on chosen weekdays, in your organization's timezone.
TriggerManual runStarts when someone presses Run. Good for drills and on-demand playbooks.
LogicConditionBranches on simple rules (all or any must match).
LogicWaitPauses for a set time, then continues.
LogicSet variablesWorks out values for later steps to reuse.
ApprovalsRequest approvalStops the run until the people you choose approve (any one of them, or all of them; from people or from a group), or anyone who can approve changes. They are emailed and see it under Approvals.
ActionsCreate incident / Update incidentOpens an incident, or posts an update or status change to one.
ActionsSend notificationEmails everyone, chosen groups or chosen recipients.
DataGet changes / Get incidentsLooks up change requests or incidents (by default the open ones) and passes the list, count and summary to later steps. Changes nothing.
ActionsHTTP requestCalls an outside https address and uses the answer in later steps. Credentials come from stored Secrets.
ActionsPost to a channelPosts to a Slack or Teams channel, or opens or resolves a PagerDuty alert (see Integrations). This uses the real service.
ControlStopEnds that branch.

Using what a webhook sends

A Webhook event trigger accepts any JSON, in whatever shape your service sends it (an UptimeRobot, Datadog or home-made payload): nothing has to be reshaped. In the trigger, press Receive test payload, then trigger the alert from your own system (for example UptimeRobot's test alert) while it listens (up to 2 minutes): the first event that arrives fills in the Example payload for you. You can also paste one by hand, or press Use the latest event received to reuse one that already arrived. Every field in the example appears under Dynamic content in the steps that follow, as {{payload.monitor.name}}, and in the Condition field picker. For example: webhook from UptimeRobot, then a Condition payload.monitorFriendlyName equals server: True opens an incident that says “{{payload.monitorFriendlyName}} is down”, False ends the run. The example is only a guide; the real event is whatever arrives. A service can also say what an event is with the headers X-Event-Kind, X-Event-Id and X-Correlation-Key. The same payload twice in a row counts as one event, and a changed payload is always treated as news.

Looking things up: Get changes and Get incidents

Get changes and Get incidents (under Data) look up what you ask for, by default the open ones, and hand the result to the steps after them: the list (one per line), the count, a summary sentence and the titles. They change nothing. Example, a Monday digest: Schedule (Mondays 09:00) → Get changes (open) → Send notification with the body {{steps.changes.list}} (twenty open changes arrive as twenty lines, one per change, such as CHG-12 · Core switch · approved · high risk · normal · Mon, Nov 16, 02:00; use {{steps.changes.summary}} for “20 open change requests” in the subject), to everyone, to a group, or to people with an account here (for example, just you), or Post to a channel for Slack or Teams. The step's Limit (default 25, up to 100) caps how many lines the list holds; when more match, the list ends with “…and N more” and the count is still the true total. The list is plain text, one item per line. To send nothing when there is nothing to report, add a Condition on count being greater than 0. The template Weekly digest: open change requests sets all of this up.

HTTP request and stored secrets

The HTTP request step calls an outside web address (GET, POST, PUT, PATCH or DELETE) and passes the answer on: status, ok, the response body, and, for JSON, each field as {{steps.<id>.response.<field>}}. It has two outputs: Succeeded (a 2xx answer) and Failed (anything else, a timeout, or a blocked address). If Failed is not connected, a failure ends the run as failed, with the reason.

  • It is deliberately restricted. Only https:// addresses on the public internet, on the standard ports; addresses that point at private networks, this server, or cloud metadata are refused (including names that resolve to them); redirects are not followed; the answer is clipped; at most 60 calls a minute per organization.
  • Credentials go in Secrets (Integrations → Secrets, Owners and Administrators). A secret is encrypted, can never be read back, is shown in a header as {{secrets.name}}, and is only ever sent to the one host it was saved for, even if a workflow is edited to send it elsewhere. Never type a token straight into a header.
  • It really calls the address when the workflow runs, a test run included. A simulation calls nothing and uses your example response instead.
  • At most once. If the server restarts in the middle of a call, the request is not repeated: the run follows Failed, saying it may or may not have been sent.

Add a secret and use it in an HTTP request

  1. Open Integrations → Secrets (Owners and Administrators; the page says if secrets are not available on this server yet) and fill in the form, then Save secret.
  2. Give it a short name (letters, numbers and underscores, for example pagerduty_key), the host it may be sent to (the Only send it to field, for example api.example.com), and paste the Value. It is encrypted at once and can never be shown again; to change it, use Replace value on its row (Delete removes it).
  3. In an HTTP request step, add a header such as Authorization with the value Bearer {{secrets.pagerduty_key}}. The real value is put in only at the moment the call is made, and only if the address is on the host you saved it for.
  4. Check with Test (nothing is called) and then a real run; the run history shows the status and answer, with secret values removed.

Approvals sent to chosen people

In a Request approval step you can choose who approves: anyone who can approve changes (the default), or chosen people and/or groups (from a group, the people who also have an account here, matched by email). Then choose whether any one of them is enough, or all must approve (one rejection rejects). They are emailed, and it appears under Approvals for them, whatever their role. Everyone else, apart from Owners and Administrators, who can always see and settle everything, does not see it.

Using values in text

Subjects and messages can include values from the run by typing them in double curly braces, for example {{incident.number}} and {{incident.title}}. The step settings list what is available at that point, so you can pick instead of typing. Only fill-in values are supported, never code.

What to know

  • A Send notification step is delivered exactly like notices from an incident: really emailed when the server has an email provider, otherwise recorded and labelled Sandbox.
  • A Post to a channel step posts for real when the workflow runs. Test shows what it would post and sends nothing. If the channel has been disabled or deleted, the step fails and says so.
  • Anyone can look at workflows. Creating and editing them, and publishing, running, pausing or cancelling, are for Owners and Administrators.
  • An automation never sets off other automations. A workflow that creates an incident will not start a second workflow, so loops cannot happen.

Integrations (webhooks)

Owners & administrators

An integration gives a monitoring tool, or any system that can make a web request, a private address to send events to. Each event is recorded, and a published automation can react to it, for example by opening an incident.

Set one up

  1. Open Integrations → New. Name it and, if you like, list the event kinds it accepts. Turn on Require HMAC signature verification if the sender can sign its requests.
  2. Copy the endpoint URL and token. The token is shown only once. If you lose it, rotate the token on the integration's page. The old one stops working immediately.
  3. Point your tool at the URL, sending the token in an Authorization: Bearer header.
  4. Build an automation with a Webhook event trigger, and publish it. The integration page shows each event received, so you can confirm it arrived.
Example request
curl -X POST 'https://YOUR-OUTAGE-APP-ADDRESS/api/v1/hooks/<id>' \
  -H 'Authorization: Bearer <your token>' \
  -H 'Content-Type: application/json' \
  -d '{"eventId":"evt-1","kind":"resource.down","correlationKey":"switch-01","attributes":{"host":"switch-01"}}'

Give each event its own eventId; the reply tells you if an event was a duplicate. The correlationKey lets automations reuse one incident for repeated alerts about the same thing. After you create the integration, copy the exact URL and a ready-made example from it.

Treat the token like a password. Anyone who has it can send events as that integration. Rotate it if it may have been shared.

Services that cannot send a header

The normal way to authenticate is the Authorization: Bearer <token> header. If a service cannot set headers, tick Also accept the token in the address on that integration, and give the service the address with ?token=<token> on the end (shown once, when you create the integration). It is off by default because an address is kept in more places than a header is: treat it like the token, and rotate the token if it ever leaks. Signed integrations still need their signature.

Repeated alerts

Monitors often send the same alert again and again. If an event is identical to the latest one (same kind, same correlation key, same attributes) and arrives within the integration's window, it is recorded as Repeat, ignored and starts nothing. The window defaults to 10 minutes and you can change it, or set it to 0 to turn it off, in the integration's settings. An alert that changed (for example severity going up), or one that follows a different kind such as resource.up, is never ignored. Put timestamps in observedAt, not in attributes, or every event looks different.

Outage App answers your monitor straight away. Opening the incident, running automations and sending notices all happen afterwards, so a slow email service never makes your monitor time out and retry.

Outbound channels: Slack, Teams and PagerDuty

The Outbound channels tab on the Integrations page sends incidents out to where your team already works. Owners and administrators set them up.

  • Slack and Microsoft Teams: paste an incoming-webhook address (Slack) or a Workflows webhook address (Teams). Outage App posts when an incident is declared, changes status (including resolved) or gets an update. You choose which of those, the lowest severity, and whether planned maintenance is included.
  • PagerDuty: paste the service's Events API v2 integration key. Outage App opens an alert when an incident is declared and resolves the same alert when the incident is resolved or closed. Timeline updates never page, and planned maintenance does not page unless you turn it on. If a resolved incident comes back, it pages again.
  • The address or key is stored encrypted and is never shown again: you only see where it points. To change it, paste a new one.
  • Send a test posts a real message (for PagerDuty, a low-severity alert that is resolved straight away) and tells you what the service answered. Each channel's Recent posts shows what was sent and the result.
Accepted is not read. A post is marked accepted when Slack, Teams or PagerDuty took it. If the connection drops while sending, the post is marked unconfirmed and is not sent again by itself, so nobody is paged twice. Check the destination and re-post from the incident if needed. If this page says channels are not available on this server yet, an administrator of the server needs to switch them on first.

Settings & activity log

Owners & administrators

Settings is for Owners and Administrators. Everyone sees the same Overview page, with the current state of things and recent events.

Settings tabWhat you do there
OrganizationOrganization name, default timezone, the support contact signature and the reply-to address (where replies to notices go). The Organization ID (shown here, with a copy button) is what to quote to support.
Users & invitationsInvite by email with a role, resend or revoke an invitation that has not been used, see members, change roles and remove people. Removing takes effect immediately. If email is off, the invitation page shows the link so you can pass it on yourself. Someone who declines an invitation shows as Declined.
DirectoryConnect your Microsoft Entra directory (an administrator of that directory approves Outage App, read-only) and choose groups. Each becomes a group here that mirrors the Entra group exactly: people added to or removed from it in Entra are added or removed here within 15 minutes, or at Sync now. People it brings in are recipients, so they cost nothing extra. Synced groups and the people in them cannot be edited by hand; Stop syncing turns a group back into a normal one, and Disconnect keeps everything as normal groups.
RecoveryHow long a monitor must stay healthy before an outage is confirmed resolved.
Usage & billingYour plan, free-trial days left, billable users, extra users and monthly total; choose or change a plan; open Stripe to update the card or download invoices. See Plans and billing below.
PoliciesWhether every change needs approval, whether requesters can approve their own changes, how long approvals wait, whether closing an incident needs a note, and the most people one notice may go to.
BrandingUpload your logo and set the footer used in emails. Send me a test email sends a real one to you (when email is on); Open full preview shows desktop and phone views.
SecurityLimit invitations to your company's email domains. Your own sign-in code and signed-in devices are under My account (below), which every person can open.
Audit exportsDownload the activity log as a file for your records.

Microsoft Entra directory sync

Instead of adding every person and building every group by hand, mirror your Microsoft Entra groups. You approve our app once, choose the groups, and Outage App keeps them in step. Owners and Administrators can do this. Your Entra administrator is needed for the approval step only.

  1. Open Settings → Directory and choose Connect Microsoft Entra. If the page says it is not available, the server has not been set up for it yet.
  2. Sign in as an administrator of your Microsoft directory (a Global Administrator or Privileged Role Administrator: only they can approve application permissions) and Accept. Outage App asks for read-only permission to read groups and their members and to read the users in them (Group.Read.All, GroupMember.Read.All, User.Read.All). It cannot change anything in your directory.
  3. Back in Outage App, Add groups…: search your directory and tick the groups to use. Each becomes a group here, with the same name, marked From Entra.
  4. Press Sync now to bring the people in straight away. After that it re-reads every 15 minutes.
  • It is an exact 1-to-1 mirror. Someone added to the Entra group is added here; someone removed in Entra is removed from the group here. Nested groups count, and a dynamic group is whatever its rule currently selects. People are never deleted by the sync; someone who ends up in no synced group simply becomes a normal, editable recipient.
  • People you already added by hand are kept, not duplicated. If an Entra person has the same email address (or the same sign-in name or another of their addresses) as a recipient you already have, that recipient is linked to them, keeps their name, and joins the synced group. A person with no Email falls back to their sign-in name.
  • One email per person. Pick several synced groups for a notice and anyone in more than one gets a single email.
  • Left out: each group says how many Entra members were left out: accounts with no email address, disabled accounts, and an address that already belongs to someone linked to a different Entra account. If the count looks wrong, press Sync now again, and check the app registration still has the three permissions with admin consent.
  • Synced groups and the people in them cannot be edited by hand (they show Manage sync instead of Edit). Stop syncing turns a group back into a normal one with its current members. Disconnect keeps everything as normal groups and stops syncing. If your directory withdraws approval, the page says so and the groups keep their last members.
  • Synced people are recipients, not users: they cost nothing extra and cannot sign in. Changing a person's role or inviting them is still done under Users & invitations.

My account, sign-in code and the change manager add-on

  • My account (your name at the bottom of the sidebar, any role) lets you turn the emailed sign-in code on or off, forget the devices you chose to remember, and sign out other sessions. With it on, a correct password is followed by a 6-digit code emailed to you (valid for 10 minutes, 5 tries); tick Remember this device to skip the code on that browser for 30 days. Resetting your password forgets all remembered devices. The code is only offered when the server can really send email; in sandbox mode the page shows the code and says no email was sent.
  • Also a change manager (Settings → Users & invitations): an Owner or Administrator can tick this for a person of any role, for example an operator. They keep their role and also can approve and reject changes. It takes effect on their very next request, and unticking it removes it just as quickly.
  • Invitations: when you sign in and someone has invited your email address, a Join <organization> card appears with Accept and Decline.

Plans and billing

  • Every new workspace gets a 14-day free trial with no card, for up to 25 billable users. A banner counts the last week down.
  • Plans are monthly: Starter $49 (3 billable users) and Team $99 (10). Both plans have every feature. Extra billable users are $8 each per month.
  • Under Usage & billing, an Owner or Administrator chooses a plan. You pay on Stripe's own secure page: Outage App never sees card details. Manage payment and invoices opens Stripe for the card, receipts and cancellation.
  • Who uses a billable seat: every person with an account, whatever their role (viewers too), and every open invitation. People who only receive notices (recipients) need no account and are free and unlimited.
  • Inviting someone beyond your seats is blocked until you add extra users there. Changes are prorated by Stripe, and you are shown the new monthly total first. You cannot go below the seats already in use.
  • If a payment fails, a warning appears and everything keeps working while Stripe retries. If the trial ends without a plan, or the subscription ends, the workspace becomes read-only: you can still see everything, but nothing can be changed, automations stop, and monitor events are not accepted, until a plan is chosen. Nothing is ever deleted.

Download or delete your data

  • Download all data (Owners): Settings → Data & deletion gives you one file (JSON) with your people, sites and services, recipients and groups, incidents and their updates, changes and approvals, notices, integrations, automations and the activity log. Passwords, tokens, channel addresses and stored secret values are never included.
  • Delete the organization (Owners): type its name to confirm. It is hidden for everyone at once, its subscription is cancelled so nothing more is charged, and the other owners and administrators are emailed. You have 14 days to press Restore this organization (or download your data); after that everything is erased permanently and cannot be recovered. If our support team deleted it, only support can restore it.
  • Delete my account (anyone, My account): signs you out everywhere, removes you from every organization and erases your name, email address and password. What you did stays, shown as “Deleted user”. You cannot do it while you are the only Owner of an organization: make someone else an Owner, or delete the organization first.
  • Suspended by support: if our team suspends an organization, everyone sees a notice instead of the app, and only Help works until support lifts it.

The activity log

Activity (Owners, Administrators and Change managers) lists who did what and when: sign-ins, role changes, incidents, approvals, settings. Entries cannot be edited or deleted, and sensitive values are hidden before they are stored.

Troubleshooting & FAQ

Help
“I sent a notice but nobody got it.”
Open the notice on the incident or the Notifications page. If it says Sandbox, the server has no email provider connected (ask whoever runs your Outage App server). If it says Accepted but not Delivered, ask the person to check spam. If it says Bounced or Blocked, correct the address under Recipients.
“I did not get my confirmation, invitation or reset email.”
Check spam, and make sure you used the address the invitation was sent to. You can request another confirmation or reset link once a minute. Links expire, so use the newest one.
“I cannot see a page, or a button is missing.”
Pages and buttons depend on your role (see Roles above). Ask an Administrator if you need more access.
“I cannot delete a site or service.”
It is still used by an incident or change. The message says which. Rename it instead, or leave it: history keeps pointing at it.
Still stuck? Press Help in the top bar (any role), choose how urgent it is, and describe what is going on. It emails our support team with your name, email address and organization, and they reply to your email address. In sandbox mode nothing is emailed and the window says so; you can always write to support@outageapp.com.
“Entra says someone was left out.”
They have no email address or sign-in name that is a real address, the account is disabled, or the address already belongs to a person linked to a different Entra account. Check the user in Entra, then press Sync now. If you just added a permission to the app registration, give it a minute and sync again.
“A planned incident I made from a change sent no notice.”
A notice only goes to the groups and people chosen in the Create planned incident dialog, with Send the planned-maintenance notice now ticked. Notices can also be sent later from the incident.
“A webhook arrived but my automation did not use the fields.”
In the Webhook trigger press Receive test payload and send a test from your service, so the fields appear as Dynamic content. Fields are used as {{payload.<field>}}.
“My approval was marked no longer valid.”
The change was edited after it was approved. Review it again and approve the new version.
Not built yet: authenticator-app and security-key sign-in (the emailed code is built), annual billing, custom roles, and importing members by CSV. These are shown as unavailable wherever they would appear.