Quick Start Guide

This article will help you get started with your new PagerDuty account. If there are any terms that are unfamiliar you may want to check out our Glossary of Terms.

Create a User Profile

To open your profile page, click your avatar in the upper right corner and click My Profile. On your profile page, there are three tabs for configuring your settings.

Contact Information

The Contact Information tab is where you add contact methods, as well as view recent incident activity. Add contact methods on this page — refer to the push notification guide to add your mobile device.


You can add a maximum of 10 contact methods, regardless of type.

Notification Rules

The Notification Rules tab is where you define how and when you are notified when an incident is assigned to you. Notification rules for high- and low-urgency incidents are configured separately. You can also receive notifications when you are going on- or off-call.

You can stagger notifications by entering an amount of time after an incident triggers.


We recommend that you set your notification rules to contact you shortly after an incident is triggered. A minimum of 2 notification rules will help make sure you do not miss a critical notification.


You can create up 20 high-urgency and 10 low-urgency notification rules.

See our best practice tips around setting up notification rules

User Settings

The User Settings tab is where you can:

  • update your login email and password.
  • add your Gravatar photo.
  • change the color to represent your schedule shifts.
  • revoke access to linked applications.

Create an On-call Schedule

On-call schedules allow you to create rotations so that users are only notified when they should be. You can create a schedule under ConfigurationSchedulesNew On-Call Schedule. Add users to the shift (schedule layer), select how frequently the shift rotates, and at what time the shift is handed off to the next user.

Create an Escalation Policy

Escalation policies determine who should be assigned to an incident and what should happen to that incident when there is no response.

These can be made under ConfigurationEscalation PoliciesNew Escalation Policy. You can add users or schedules to the levels of your policy. If an incident is not ack'ed or resolved within the acknowledgement timeout period, it will escalate to the next level. You can also set how many times you'd like an escalation policy to repeat.

Create Teams

Teams allow you to organize and filter views in the mobile and web app. This feature is available on Business and Digital Operations plans.

You can create a team under ConfigurationTeamsNew Team. Associate the Team with an escalation policy, and it'll automatically associate it with relevant users, schedules, and services. You can manually add or remove users, too, at any time.

Create a Service

Services represent an area of your application. You can have one or more integrations on a service. Each service is associated with a single escalation policy.

  1. Go to ConfigurationServicesAdd New Service.

  2. Give the service any name, and choose an integration type when prompted.

  3. Choose an escalation policy to use for this service, and customize other incident settings as needed.

  4. Follow the instructions to set up the integration. If the monitoring tool you are using does not appear on the list, you can follow the generic email integration guide. Alternatively, you can select Use our API directly. If your service is able to make basic HTTP API calls, then you can interact directly with our API to trigger, acknowledge, and resolve incidents. Our developer documentation provides several examples of how to integrate with PagerDuty using our API.

On a service's Integrations tab, click New Integration to add more integrations.

To test the settings you have created in your new PagerDuty account, you can trigger an incident using our guide: Triggering an Incident with Web UI, Email, or API.

Quick Start Guide

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.