Skip to content

Commit

Permalink
Playbooks v1 vs v2 clarifications
Browse files Browse the repository at this point in the history
  • Loading branch information
cwarnermm committed Sep 11, 2024
1 parent be1b8ac commit 4601df1
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions source/guides/repeatable-processes.rst
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,10 @@ Build repeatable processes
.. include:: ../_static/badges/ent-cloud-selfhosted.rst
:start-after: :nosearch:

.. important::

Mattermost v10 introduces Playbooks v2 which is available for all Enterprise licensed customers. Playbooks v1 will continue to be packaged for all deployments, including Team Edition and Professional on :doc:`supported Mattermost server releases </about/mattermost-server-releases>`. New playbooks features & security updates will only be added to Playbooks v2.

Use collaborative playbooks in Mattermost to provide structure, monitoring and automation for repeatable, team-based processes integrated with the Mattermost platform. Playbooks are :doc:`configurable checklists </repeatable-processes/work-with-tasks>` for teams to achieve :doc:`specific and predictable outcomes </repeatable-processes/metrics-and-goals>`, such as incident response, software release management, and logistical operations.

Playbooks monitor channels for keywords or user actions to trigger a structured process, which brings up a set of individual or shared tasks, each associated with manual or automated actions. As playbooks are executed, some may have requirements for :doc:`broadcasting status updates to stakeholders </repeatable-processes/notifications-and-updates>` at regular intervals, to populate workflow dashboards by conducting :ref:`retrospectives <repeatable-processes/metrics-and-goals:configure retrospectives before a run>` after the core process is complete, or other customer requirements as exit criteria for a :doc:`playbook “run” </repeatable-processes/work-with-runs>`.
Expand Down

0 comments on commit 4601df1

Please sign in to comment.