Allma

Sign in

🔀 Workflows

What is a workflow?

A workflow is a system containing a set of interdependent events, components, and actions configured in a permutation to apply to a specific organizational use case at a specific point in time alongside metadata that informs configuration.

Which workflows are available?

Allma provides the user with a technical incident workflow out of the box that may be configured to the team’s satisfaction.

View the 🛠️ Technical incident workflow’s default configuration

Roles

Incident commander

The primary decision maker for the incident, listening to hypotheses and data presented by participants and delegating actions.

Communications lead

The core communicator for the incident, conveying status, updates, and technical details to stakeholders, support personnel, and/or customers.

Participant

Team member available to investigate, carry-out actions delegated by the Incident Commander, and actively work towards incident mitigation.

Watcher

Team member with knowledge or guidance that might contribute to resolution, but is not available to actively investigate or carry-out mitigative actions.

Severity levels

SEV-0

Severe service outage. Service functionality considered down for all or large portions of customers.

SEV-1

Service outage or degradation that impacts customers.

SEV-2

Service or tool outage or degradation that impacts employees, vendors, partners, or other internal stakeholders.

SEV-3

Service or tool outage that has minimal or no impact but requires a response.

Beyond the customizable technical incident workflow, Allma also provides a number of curated workflows which cannot be customized at this time. Workflows can be accessed via /allma new in Slack.

View the 🎡 Sandbox workflow

Basics

  • Description: Easily play around with Allma in a safe space with your team.
  • Channel prefix: sandbox
  • Privacy: public

Roles

Incident commander

The primary decision maker for the incident, listening to hypotheses and data presented by participants and delegating actions.

Communications lead

The core communicator for the incident, conveying status, updates, and technical details to stakeholders, support personnel, and/or customers.

Participant

Team member available to investigate, carry-out actions delegated by the Incident Commander, and actively work towards incident mitigation.

Watcher

Team member with knowledge or guidance that might contribute to resolution, but is not available to actively investigate or carry-out mitigative actions.

Severity levels

SEV-0

Severe service outage. Service functionality considered down for all or large portions of customers.

SEV-1

Service outage or degradation that impacts customers.

SEV-2

Service or tool outage or degradation that impacts employees, vendors, partners, or other internal stakeholders.

SEV-3

Service or tool outage that has minimal or no impact but requires a response.

View the 🎲 Tabletop workflow

Basics

  • Description: Refresh your organization on your incident management program or onboard new engineers.
  • Channel prefix: tabletop
  • Privacy: public

Roles

Tabletop manager

The primary organizer and gamemaster for the tabletop exercise, presenting data and context to simulate a real-life incident without interfering with the flow of the incident, and ensuring that participants stay focused and within the scope of the exercise.

Incident commander

The primary decision maker for the incident, listening to hypotheses and data presented by participants and delegating actions.

Communications lead

The core communicator for the incident, conveying status, updates, and technical details to stakeholders, support personnel, and/or customers.

Participant

Team member available to investigate, carry-out actions delegated by the Incident Commander, and actively work towards incident mitigation.

Watcher

Team member with knowledge or guidance that might contribute to resolution, but is not available to actively investigate or carry-out mitigative actions.

Severity levels

SEV-0

Severe service outage. Service functionality considered down for all or large portions of customers.

SEV-1

Service outage or degradation that impacts customers.

SEV-2

Service or tool outage or degradation that impacts employees, vendors, partners, or other internal stakeholders.

SEV-3

Service or tool outage that has minimal or no impact but requires a response.

View the 🔒 Security incident workflow

Basics

  • Description: Start a private channel to run your security investigations.
  • Channel prefix: investigation
  • Privacy: private

Roles

Incident commander

The primary decision maker for the incident, listening to hypotheses and data presented by participants and delegating actions.

Communications liaison

The core communicator for the incident, conveying status, updates, and technical details to stakeholders, support personnel, and/or customers.

Deputy

Security personnel working on the investigation, carrying out actions delegated by the Incident Commander, and actively working towards remediation.

Watcher

Team members with knowledge or guidance that might contribute to resolution (i.e. Legal, Compliance, CISO, Engineering Leaders).

Severity levels

SEV-0

Critical threat may have been detected, impacting mission critical endpoints. Requires immediate investigation.

SEV-1

Major threat may have been detected, impacting a few top priority endpoints. Requires immediate investigation.

SEV-2

A threat may have been detected, impacting a few endpoints. Requires further investigation during business hours.

SEV-3

A minor threat may have been detected, impacting a few non-mission critical endpoints. Further investigation should be performed during business hours.

View the ❗ Customer escalation workflow

Basics

  • Description: Bring your organization together for troubleshooting customer reported bugs or a customer escalation.
  • Channel prefix: sandbox
  • Privacy: public

Roles

Incident commander

The primary decision maker for the bug report or escalation, listening to hypotheses and data presented by participants and delegating actions.

Communications liaison

The core communicator between internal teams, conveying consumable status and updates for technical and non-technical teams.

Customer facing lead

The bridge between your company and the customer, preparing and distributing external facing status updates.

Technical participant

Team member available to troubleshoot, carry-out actions delegated by the Incident Commander, and actively work towards a solution

Watcher

Team member with knowledge or guidance that might contribute to resolution, but is not available to actively investigate or carry-out mitigative actions.

Severity levels

High

Critical mass of tickets reported by customers with the same symptoms, or a business critical customer(s) is experiencing service degradation. Requires all hands on deck until issue(s) is resolved or has concrete next steps.

Medium

Multiple tickets reporting the same symptoms or an escalated customer(s) experiencing service degradation. Requires quicker turnaround time on issues and next steps.

Low

Several tickets reporting the same symptoms or internally observed service degradation impacting a subset of customers. Requires a proactive approach to address issues.

View the 🐛 Bug bash workflow

Basics

Description: Collaborate to discover bugs before they make it to production

Channel prefix: bugbash

Privacy: public

Roles

Bug bash commander

Primary decision maker + delegator

Engineering Lead

Holds technical knowledge. Collaborates with Bug Bash Commander to identify + record bugs

Participant

Stress test feature(s). Identify + record bugs. Provide relevant artifacts (screenshot, link…)

Severity levels

Major Change

Net new functionality, might break old functionality

Change

Material evolution of existing feature(s)

Minor change

Enhancement or alteration to existing feature

View the 🎥 Sprint project workflow

Basics

  • Description: Collaborate and run a sprint project
  • Channel prefix: sprint-proj
  • Privacy: public

Roles

Sprint project commander

Responsible for delivering the project on time

Engineering lead

Technical expert for the project

Product manager

Product expert for the project

Participant

Contributor to the project

Watcher

Project observer

Severity levels

Major Change

Net new functionality, might break old functionality

Change

Material evolution of existing feature(s)

Minor change

Enhancement or alteration to existing feature

View the 🚀 Release workflow

Basics

  • Description: Coordinate across stakeholders while running a release
  • Channel prefix: release
  • Privacy: public

Roles

Release commander

Leads team through release

Engineering lead

Technical expert for the project

Communications liaison

Keeps stakeholders infromed throughout release

Customer advocate

Keeps customers updated on release

Participant

Helps the release process

Watcher

Observes the release process

Severity levels

Major Change

Net new functionality, might break old functionality

Change

Material evolution of existing feature(s)

Minor change

Enhancement or alteration to existing feature

View the 🧑‍💻 Code review workflow

Basics

  • Description: Keep stakeholders in the loop while reviewing contributions
  • Channel prefix: code-review
  • Privacy: public

Roles

Reviewer

Code reviewer

Submitter

Engineer submitting code for review

Severity levels

Major Change

Net new functionality, might break old functionality

Change

Material evolution of existing feature(s)

Minor change

Enhancement or alteration to existing feature

View the 📝 Engineering offboarding workflow

Basics

  • Description: Run offboarding across your Engineering team. Ensure employees have a positive experience
  • Channel prefix: offboarding
  • Privacy: private

Roles

Bug bash commander

Primary decision maker + delegator

Severity levels

High risk

Employee leaving on negative terms, sensitive or messy situation

Medium risk

Material evolution of existing feature(s)

Low risk

Employee leaving in good faith or straightforward situation

Favorite workflows

Mark the workflows your team uses most frequently by adding them to your favorites. Favorite workflows will always appear when kicking off a workflow (i.e. /allma new).

Manage your favorite workflows

Admins can manage their teams favorites here: https://app.allma.io/settings/workflows

fav_workflows.avif

How do I kick off a workflow?

via 🤖 Slash commands

/allma new [instance name] — Declare a new workflow instance and create a channel. (Optional) Any text, including spaces, after new will be used as the incident name.

allma_new.avif

via 🧵 Alert thread actions

Allma will offer quick actions in response to other Slack apps within your workspace.

Quick actions will appear in threads when those apps send messages to your Slack if Allma is also present in that channel.

Example:

via_alert_thread_action.avif

via Allma’s “app home”

Navigate to the “Allma” app in your Slack sidebar, then choose New workflow instance

via_app_home.avif

via Slack’s search

Search Slack (CTRL/CMD K) for Declare new incident

declare_new_incident.avif

via Slack’s shortcuts button

Search for Declare new incident in the “+” menu, found below the message box in Slack

slack_plus_icon.avifdelcare_new_incident.avif

our newsletter is cool

allma, inc © 2022