Task Games - Helm User Guide

What Are Task Games?

Task games attach a randomized mechanic to a task. Instead of a fixed requirement, the task's outcome — or even its requirement itself — is determined by chance at the moment the assignee plays the game. Helm supports four game types: dice roll, coin flip, spinner, and pop.

Task creators configure the game when creating or editing a task. Only the task's assignee can play the game; the creator observes the result.

✓ One Play Per Assignment

Each assignee gets one opportunity to play the game on a given task. The result is recorded and cannot be replayed (except where a reroll option is explicitly configured).

Attaching a Game to a Task

Games are configured in the task creation or edit form, under the "Task Game" section at the bottom of the form.

Enable the Game

Check "Enable game for this task" to expand the game configuration panel.
Select a Game Type

Choose one of the four game types: Dice Roll, Coin Flip, Spinner, or Pop. The configuration form updates to match the selected type.
Configure Outcomes

Fill in the outcome labels for each possible result (e.g., what each die face means, what heads and tails mean, what each spinner segment is).
Set Game Options

Configure behavior options: whether the game is required before submission, whether the outcome becomes the task requirement, who can see results, and more.
Save the Task

The game configuration is saved with the task. The assignee will see the game panel when they open the task.

The Four Game Types

Dice Roll

The dice roll game uses up to three six-sided dice. For each die, the creator assigns a label to each of the six faces (1 through 6). When the assignee plays, all configured dice are rolled simultaneously. The result labels for each die are displayed after rolling.

Up to three dice: Die 1 and Die 2 are always present; Die 3 is optional.
Per-face labels: Each face value (1–6) on each die has its own label. Labels define the meaning of that result (e.g., face 3 on Die 1 might mean "10 minutes of corner time").
Allow reroll on 6: An optional setting that grants the assignee one reroll if any die lands on 6.

Coin Flip

The coin flip presents two outcomes: heads and tails. The creator writes a label for each side, defining what each result means for the task. The assignee taps to flip; the coin animates and lands on one side. The result label is displayed immediately.

Simple binary outcome — useful for two-option choices.
Both the heads label and tails label are required before saving.

Spinner

The spinner presents a configurable wheel with labeled segments. The assignee taps to spin; the wheel animates and lands on one segment. The creator defines the segments:

Segments: Each segment has a label and an optional color. The default configuration starts with six segments.
Add or remove segments: The creator can add more segments or remove existing ones to match the number of outcomes needed.
Segment colors: Each segment can be given a color for visual distinction on the wheel.

Pop

Pop is a time-based challenge rather than an on-demand game. When a task has a pop game configured, the system sends the assignee a push notification at a random time within a configured interval. The assignee must acknowledge the pop within a set deadline. Missing the deadline is a failed pop.

Pop is configured with four groups of settings:

Setting	Description
Minimum Interval	The shortest time (in minutes) that can elapse between pops. Minimum 5 minutes.
Maximum Interval	The longest time (in minutes) between pops. Cannot exceed 1,440 minutes (24 hours).
Response Deadline	How long (in minutes) the assignee has to acknowledge a pop before it expires. Maximum 60 minutes.
Active Hours	The time window during which pops may trigger (in the assignee's timezone). Can be set to 24/7 with no time restrictions.
Active Days	Which days of the week pops may trigger. Default is Monday through Friday.
Max Daily Pops	The maximum number of pops that can trigger on any one day. Can be set to unlimited.

✓ Pop Completion Requirement

When a pop triggers, all assignees receive a notification and must confirm within the deadline. The pop confirmation becomes a task requirement automatically — this behavior is fixed and cannot be disabled for the pop game type.

Game Options (Dice, Coin, Spinner)

The following options apply to dice roll, coin flip, and spinner games. Pop has its own fixed completion behavior described above.

Option	Effect
Required before submission	The assignee must play the game before they can submit the task for completion.
Outcome becomes the requirement	The result of the game determines the task's requirement. Until the game is played, the task shows "Play the game to reveal your requirement." After playing, the requirement is displayed prominently. This replaces any fixed task requirement.
Show possible outcomes	The full table of outcomes (all die faces, both coin sides, all spinner segments) is visible to the assignee before they play. Useful when the outcomes are informational rather than surprising.
Show results to assignee	The assignee can see the result after playing.
Show results to task creator	The creator can see the result the assignee rolled or flipped.
Allow reroll on 6 (dice only)	If any die shows a 6, the assignee may choose to reroll all dice once.

How Results Affect Task Outcomes

The relationship between a game result and the task depends on which options the creator enabled:

When "Outcome becomes the requirement" is on

The game result is treated as the task's requirement text. The assignee sees a highlighted panel labeled "Your Requirement" after playing. They must then complete whatever the result specifies before submitting the task. The requirement panel shows who played and when.

When "Required before submission" is on

The task cannot be submitted until the game has been played. The submission button or flow is gated behind a played state.

When neither is on

The game is informational or purely for entertainment. Results are recorded but do not gate submission and do not override the task's written requirement.

Playing a Game as an Assignee

When you open a task that has a game configured, the game panel appears at the top of the task detail view. The experience depends on the game type:

Dice Roll: Tap the roll button. The dice animate and land on their values. Result labels appear for each die.
Coin Flip: Tap the flip button. The coin animates and shows the result label for heads or tails.
Spinner: Tap the spin button. The wheel spins and stops on a segment. The segment label is displayed as the result.
Pop: You do not initiate a pop manually. You receive a push notification when a pop triggers and must acknowledge it within the configured deadline.

⚠ One Play Only

After playing, the game panel switches to a result display and the play button is no longer available. Results cannot be changed after submission. The dice reroll option (if enabled) is the only exception — it allows a single additional roll if a 6 appears.

Points and Task Games

Task games do not directly change how points are awarded for a task. Points are determined by the task's configuration (point value, completion criteria) in the normal task flow. However, if a game outcome becomes the task requirement ("Outcome becomes the requirement" is on), completing that outcome-driven requirement is what satisfies the task for points purposes — the game result sets the bar, and meeting that bar earns the points.

Point values and point configuration are covered in the standard task documentation.

Role Mapping (Advanced)

When the Task Games Role Mapping feature is enabled for your organization, creators can map specific game outcomes to participants by role. This allows different results to apply to different people in multi-participant task scenarios. Role mapping is a platform configuration option; contact your administrator if you do not see it.

Viewing Past Results

Once a game has been played, the result is stored on the task record. Anyone who has permission to see results (governed by the "Show results to assignee" and "Show results to creator" options) can view the result and the timestamp of play by opening the task.