Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.incident.io/llms.txt

Use this file to discover all available pages before exploring further.

Workflows can be used to automate parts of your incident response, such as sending email communications or escalating to an on-call rota. By default, workflows won’t run on private incidents. This is because certain workflow steps – like emailing information about an incident to a mailing list, or inviting people to the channel – could bypass the membership protections that apply to private incidents. However, you can enable this feature as an account Owner.

​
Turning on workflows on Private Incidents

If you’re sure you want to run a workflow against private incidents, we permit account owners to create private workflows. All the owner needs to do is open “Advanced settings” and press the “ Run on private incidents ” toggle: Once enabled, this workflow will apply to both private and public incidents. A common use case for private workflows is automatically adding specific members to private incidents. For example, you can configure a workflow to add your security team to all private security incidents, ensuring the right people have access without manual invitation. The responsibility is on the account owner to ensure the workflow is safe, and doesn’t expose more of the private incident than they intend.

​
What do non-Owners see?

We restrict this feature to account owners as only those users are able to see all incidents, irrespective of privacy settings. Other users will be able to see the private workflows, but will be presented with a banner warning that only account owners may modify them: If they mouseover any of the buttons, they’ll be presented with a clear warning, to make it obvious why they can’t take this action: