Skip to main content
Manage the policies that encode how your organisation should handle incidents. A policy scopes itself to a set of resources with conditions, states the requirements those resources must meet, and describes who to chase when they don’t. Every policy has a policy_type, which selects exactly one matching configuration block: a follow_up policy carries follow_up config, a schedule policy carries schedule config, and so on. Sending a block that doesn’t match the policy type is rejected.

The policy object

conditions
object[]
required

Conditions which determine which resources are in scope for this policy

Example:
created_at
string<date-time>
required
Example:

"2021-08-17T13:28:57.801578Z"

id
string
required

Unique ID of the policy

Example:

"01G0J1EXE7AXZ2C93K61WBPYEH"

name
string
required

Human readable name of the policy

Example:

"Critical incidents must export follow-ups"

policy_type
enum<string>
required

Type of the policy, specifying what this applies to

Available options:
debrief,
follow_up,
on_call_readiness,
post_mortem,
schedule,
vacation_conflict
Example:

"follow_up"

status
enum<string>
required

Disabled policies stop evaluating but keep their config

Available options:
enabled,
disabled
Example:

"enabled"

updated_at
string<date-time>
required
Example:

"2021-08-17T13:28:57.801578Z"

assignment_rules
object
Example:
debrief
object

Set when policy_type is debrief.

Example:
description
string

Human readable description of the policy

Example:

"All critical incidents must export follow-ups to an external issue tracker before 7 days has passed since closure."

expressions
object[]

The expressions relating to this policy

Example:
follow_up
object

Set when policy_type is follow_up.

Example:
on_call_readiness
object

Set when policy_type is on_call_readiness. The assignee is always the user in violation and cannot be configured.

Example:
post_mortem
object

Set when policy_type is post_mortem.

Example:
schedule
object

Detects gaps in on-call coverage. Set when policy_type is schedule.

Example: