|
| 1 | +--- |
| 2 | +title: Incident Response Billing |
| 3 | +further_reading: |
| 4 | +- link: "/service_management/incident_management/" |
| 5 | + tag: "Documentation" |
| 6 | + text: "Incident Management" |
| 7 | +- link: "/service_management/on-call/" |
| 8 | + tag: "Documentation" |
| 9 | + text: "On-Call" |
| 10 | +- link: "/service_management/status_pages/" |
| 11 | + tag: "Documentation" |
| 12 | + text: "Status Pages" |
| 13 | +--- |
| 14 | + |
| 15 | +## Overview |
| 16 | + |
| 17 | +Datadog's [Incident Management][1], [On-Call][2], and Incident Response SKUs use a seat-based billing model. |
| 18 | + |
| 19 | +Organizations have two options for incident response billing: |
| 20 | +- Incident Management or On-Call as separate SKUs, each billed individually |
| 21 | +- The Incident Response bundle, which unifies billing for both Incident Management and On-Call under a single SKU |
| 22 | + |
| 23 | +Each product bills by seat, so each user who performs qualifying actions requires a seat license. For detailed pricing information, see the [Incident Response pricing page][3]. |
| 24 | + |
| 25 | +View and manage seat usage for each product in the [Seat Management][4] section of the Plan & Usage page in Datadog. |
| 26 | + |
| 27 | +## Allocate seats |
| 28 | + |
| 29 | +A **seat** is a license for a user to actively participate in the on-call or incident management process in Datadog. |
| 30 | + |
| 31 | +Any user can claim a seat for On-Call, Incident Management, or Incident Response as they perform actions that require a seat. Billing admins can also assign seats ahead of time to simplify the process for their teams. |
| 32 | + |
| 33 | +A user needs an **On-Call seat** if they perform any of the following: |
| 34 | +- Participate in an [on-call schedule][5] |
| 35 | +- Are included in an [escalation policy][6] |
| 36 | +- Have set up [notification preferences][7] to receive pages |
| 37 | + |
| 38 | +In the On-Call product, a user does not need a seat to view existing pages, escalation policies, teams, or schedules. |
| 39 | + |
| 40 | +A user needs an **Incident Management seat** if they perform any of the following actions. These actions require a seat whether they are performed in the Datadog UI or through integrations such as Microsoft Teams or Slack. |
| 41 | +- Modify an incident (for example, update severity) |
| 42 | +- Add a comment, graph, or link to an [incident timeline][8] |
| 43 | + |
| 44 | +In Incident Management, a user does not need a seat to create incidents, view incidents, or join incident channels. |
| 45 | + |
| 46 | +If your organization has committed to the Incident Response SKU, any user who meets the On-Call or Incident Management criteria can claim or be assigned an **Incident Response seat**. |
| 47 | + |
| 48 | +## Manage seats |
| 49 | + |
| 50 | +The [Seat Management page][1] gives billing admins visibility and control over users who occupy seats for Incident Management, On-Call, or the Incident Response bundle. |
| 51 | + |
| 52 | +The Seat Management page contains tabs for each product enabled in your organization. Depending on your contract, you may see one of the following: |
| 53 | +- Separate tabs for Incident Management and On-Call |
| 54 | +- A single tab for Incident Response (if you use the bundle SKU) |
| 55 | + |
| 56 | +Each tab includes: |
| 57 | +- A header showing the total seats in use and your committed seat count (for example, 130 of 180 seats in use) |
| 58 | +- A table listing all users who occupy seats, including: |
| 59 | + - Name |
| 60 | + - Email |
| 61 | + - Upgraded date (when the user was assigned a seat) |
| 62 | + |
| 63 | +You can also find users by searching by name, email, or team. |
| 64 | + |
| 65 | +### Assign seats |
| 66 | + |
| 67 | +Billing admins, or users with the `billing_edit` permission, can manually assign seats so team members have access before they need it. |
| 68 | + |
| 69 | +To assign a seat: |
| 70 | +1. Go to **Plan & Usage** → **Seat Management**. |
| 71 | +2. Select the relevant product tab: **Incident Management**, **On-Call**, or **Incident Response**. |
| 72 | +3. Click **Assign Seats**. |
| 73 | +4. Search for users by name or email, and select them. |
| 74 | +5. Click **Assign Seats**. |
| 75 | + |
| 76 | +Assigned users immediately appear in the Seats table and can access the product's features. |
| 77 | + |
| 78 | +### Unassign seats |
| 79 | + |
| 80 | +To remove users and free up seats: |
| 81 | +1. In the Seats table, check the box next to one or more users. |
| 82 | +2. Click **Unassign Seats**. |
| 83 | +3. Confirm your selection. |
| 84 | + |
| 85 | +After they are unassigned, the user loses access to features that require a seat. They can still perform the following actions: |
| 86 | +- Create incidents |
| 87 | +- View incidents |
| 88 | +- Join incident channels |
| 89 | + |
| 90 | +### Claim a seat |
| 91 | + |
| 92 | +When you try to perform an action that requires a seat (such as joining an On-Call schedule, updating an incident, or adding information to an incident timeline) Datadog prompts you to claim a seat. Claiming a seat requires at least one of the following permissions: `billing_read`, `on_call_read`, or `incident_read`. |
| 93 | + |
| 94 | +After you claim a seat, the following items change in Datadog: |
| 95 | +- You immediately gain access to the product features you need (for example, receiving pages or managing incidents). |
| 96 | +- The Seat Management page for your organization shows your seat assignment. |
| 97 | + |
| 98 | +If your organization has committed seats available, you occupy one of them. If all committed seats are already in use, the new assignment succeeds, but the additional seat counts as an on-demand seat. |
| 99 | + |
| 100 | +You only need to claim a seat once. After a seat is assigned, you continue to have access until a billing admin unassigns it. |
| 101 | + |
| 102 | +## Billing and overages |
| 103 | + |
| 104 | +Datadog bills for On-Call, Incident Management, and Incident Response based on the total number of seats in use during each billing period. |
| 105 | + |
| 106 | +Each billing period reflects the maximum number of concurrently assigned seats across your organization for that product. Your contract includes a committed number of seats, and any usage beyond that amount is billed at your on-demand rate. |
| 107 | + |
| 108 | +After a user claims a seat, the seat remains active and is billed month-to-month until it is unassigned. If a user is removed during a given month, the seat remains billable for that month. In the following month's billing cycle, the seat will no longer appear. |
| 109 | + |
| 110 | +You can add or remove seat licenses at any time. Removing a user before the end of a billing period prevents future charges for that seat. |
| 111 | + |
| 112 | +### Example |
| 113 | + |
| 114 | +- Your contract includes 182 committed seats. |
| 115 | +- Your organization's peak usage during the month was 190 seats. |
| 116 | + |
| 117 | +Your monthly bill contains the following: |
| 118 | +- 182 seats are billed at your committed rate. |
| 119 | +- 8 seats are billed at your on-demand rate for that billing cycle. |
| 120 | + |
| 121 | +## Further Reading |
| 122 | + |
| 123 | +{{< partial name="whats-next/whats-next.html" >}} |
| 124 | + |
| 125 | +[1]: /service_management/incident_management/ |
| 126 | +[2]: /service_management/on-call/ |
| 127 | +[3]: https://www.datadoghq.com/pricing/?product=incident-response#products |
| 128 | +[4]: https://app.datadoghq.com/billing/seats |
| 129 | +[5]: /service_management/on-call/schedules/ |
| 130 | +[6]: /service_management/on-call/escalation_policies/ |
| 131 | +[7]: /service_management/on-call/profile_settings/#notification-preferences |
| 132 | +[8]: /service_management/incident_management/investigate/timeline |
0 commit comments