Points & Store
Overview
The points system awards members points for completing task items. Points fuel an optional leaderboard and an optional store where members can redeem points for rewards defined by Root. All three components are behind separate feature flags and can be enabled independently.
Requires:
points_systemfeature flag (master switch). The leaderboard and store flags only do anything whenpoints_systemis also on.
Feature flags
| Flag | What it controls |
|---|---|
points_system | Master switch. Enables point awards on task completion. |
show_points_to_users | Shows members their own point balance in the dashboard stat card and their profile. Requires points_system on. |
leaderboard_enabled | Shows a weekly leaderboard on the dashboard ranking all members by points. When off, members can still see their own score but not others’. |
store_enabled | Enables the Store nav item and redemption flow. |
Two types of points
Ziptask has two independent point fields on every task item:
| Field | Purpose | Who sets it |
|---|---|---|
| Reward Points | Gamification currency — awarded to the member who completes the item. Drives the dashboard stat card, leaderboard, and store balance. | Admin / Root |
| Estimated Effort Points | Work estimation — represents the effort weight of the item. Used by the Projects feature to calculate estimated vs. earned costs. Has no effect on member balances. | Admin / Root |
Both fields are gated by the points_system flag. Reward Points and Estimated Effort Points are fully independent — changing one does not affect the other.
Points (rewards)
How reward points are earned
Reward Points are awarded when a member transitions a task item from DOING to COMPLETED. If a COMPLETED item is reset to TODO (by Admin/Root), the reward points are automatically reversed.
Retroactive point adjustments
Admin and Root can change the Reward Points value on a COMPLETED item at any time. The adjustment is applied automatically:
- Increase — the delta is immediately awarded to the member who did the work.
- Decrease — the delta is immediately deducted from the member’s balance. The deduction is floored at zero: if the member has already spent the points, the balance will not go negative.
Points are always attributed to the member who was assigned the item (the doer). For items that required approval, this is the member who completed the work, not the admin who approved it.
Point visibility
When show_points_to_users is on, members can see their own reward point balance in the dashboard stat card and their profile. When leaderboard_enabled is also on, everyone can see all members’ weekly totals on the leaderboard.
Points history
When points_system is on, members can view a full audit trail of their own reward points activity from their profile page (Profile → Points tab). Each entry shows the action type, the task item title or store item name, the points earned or spent, and the date. The list is paginated and supports infinite scroll.
Permissions — Points
| Action | User | Admin | Root |
|---|---|---|---|
| Earn points (task completion) | ✓ | ✓ | ✓ |
| View own point total | ✓ | ✓ | ✓ |
| View own points history | ✓ | ✓ | ✓ |
| View leaderboard (when enabled) | ✓ | ✓ | ✓ |
Store
Requires:
points_system+store_enabledboth on.
How it works
Root creates a catalogue of redeemable items, each with a point cost. Members browse the store, request redemptions, and Root approves or rejects them.
Redemption flow:
- Member clicks Redeem on a store item.
- Points are deducted from the member’s balance immediately.
- The redemption is created in Pending status.
- Root reviews pending redemptions and either Approves or Rejects.
- If rejected, the points are automatically refunded.
Redemption statuses
| Status | Meaning |
|---|---|
| Pending | Awaiting Root review |
| Approved | Granted by Root; points remain deducted |
| Rejected | Denied by Root; points automatically refunded |
Permissions — Store
| Action | User | Admin | Root |
|---|---|---|---|
| Browse store items | ✓ | ✓ | ✓ |
| Redeem an item | ✓ | ✓ | ✓ |
| View own redemption history | ✓ | ✓ | ✓ |
| Create / edit / deactivate items | ✗ | ✗ | ✓ |
| View all redemptions | ✗ | ✗ | ✓ |
| Approve / reject redemptions | ✗ | ✗ | ✓ |
Store items
Root can create items with a title, optional description, and point cost. Items can be deactivated to hide them from the store without deleting them. There is no quantity limit — items are unlimited.
Support notes
- If a member’s points look wrong, check whether any COMPLETED → TODO transitions were made recently (those reverse points automatically), or whether an Admin/Root edited the Reward Points value on a completed item (increases award the delta, decreases deduct it).
- If a member can’t see the Store nav item, verify both
points_systemandstore_enabledare on in Account → Settings. - Rejected redemptions automatically refund points — Root does not need to do anything extra after rejecting.
- Store items set to inactive are hidden from members but remain visible to Root for management.