# NIZU modules and apps connected to Gamify > Gamify does not store a separate record of what your team did. It reads the modules you already use. This page lists everything it connects to and what it takes from each. (Apps: Gamify) - Page: https://dashboard.nizu.io/knowledge_base/view/225-nizu-modules-and-apps-connected-to-gamify - Part of: [Knowledge base](https://dashboard.nizu.io/knowledge_base/llms.txt) on NIZU — https://dashboard.nizu.io/llms.txt - Updated: 2026-10-25T11:50:03Z ## NIZU modules and apps connected to Gamify Gamify does not store a separate record of what your team did. It reads the modules you already use. This page lists everything it connects to and what it takes from each. ### Core NIZU modules #### Tasks The primary XP source. Gamify awards XP when a task is moved to **Done**, weighted by the task's own **points** (story points) so effort is respected rather than raw task count. A bonus is added when the task is completed before its deadline. The assignee is credited, not whoever clicked the button, so an administrator closing a task on somebody's behalf still credits the right person. Task deadlines are also the source of the optional deadline-extension penalty. Tasks are also what a duel can be **wagered** on, when an administrator has enabled task wagers. A lost wager reassigns the task through the normal Tasks path, so its history, its notifications and its activity log all behave exactly as they would for any other reassignment and a manager can move it back the same way. #### Projects When a project's status becomes **Completed**, XP is shared among its project members. Project membership is read live from the project's member list. #### Support Tickets Closing a ticket awards XP. An open ticket can also be wagered on a duel. Gamify checks the other player's *role* first: a ticket is only offered if their permissions would let them hold it all tickets, assigned-only, or a specific ticket type that matches. Handing somebody a ticket they cannot open would make the wager impossible to honour, so those combinations never appear in the picker. #### Invoicing Recording an invoice payment awards XP to whoever recorded it. #### Estimates and Proposals An estimate or proposal moving to **Accepted** awards XP. #### Leads and Clients Converting a lead into a client awards XP. This is detected from the platform's own "client created from lead" event rather than by guessing at a status change. #### Timesheets Logging time awards a small daily amount, capped at once per day so it rewards the habit rather than the hours. #### Knowledge Base and Help Articles Publishing knowledge-base or help articles earns **documentation trophies** one family for how many you have published, another for how widely your best article is read. Deliberately no XP: paying per article would be the easiest thing in the system to game. Progress is read live from the articles themselves, so a back catalogue written long before Gamify was installed counts from the moment it is switched on. #### Messages, Files and Announcements Project and ticket comments, project file uploads, timeline posts and announcements all award small amounts of XP with hard daily caps, because these are the easiest actions to farm. #### Leave Approved leave is read so that a streak is *paused* rather than broken while somebody is away. Weekends are treated the same way. #### Team Team membership drives the Teams view of the leaderboard, which shows both total and per-member average XP. #### Team Members and Roles Gamify adds a **Gamify** tab to every staff profile showing that person's level, season XP, streak and trophy cabinet. It also adds two role permissions (manage gamification, view the leaderboard) to the standard role editor, and a **Hide me from the leaderboard** option to each user's own preferences. #### Dashboard Two dashboard widgets are provided: **My XP** (level, XP bar, rank and streak) and **Top players** (the current podium). #### Other NIZU apps #### Live Testing Optional. When the LiveTesting app is installed, a **confirmed** test regression can subtract XP. Gamify uses the regression's own build window (last good build to failing build) to attribute it to whoever caused it. An administrator can switch this to charge the test-case author instead, though that is not recommended it penalises people for writing tests that work. A regression later marked **dismissed** automatically reverses the penalty. #### Sales Commission Optional. When the Sales Commission app is installed, Gamify reads sales objectives and, at the end of each objective period, awards XP for hitting the target or subtracts XP for missing it by more than 10%. Only staff who actually have an objective are affected. #### Marvin Optional. When the Marvin app is installed and a team member has linked their own Telegram DM with Marvin, Gamify sends that person private messages about levels, trophies, notable XP changes and penalties (including confirmed test regressions). Penalties are only ever sent privately never to a shared channel. #### Telegram Notification Optional. When the Telegram Notification app is configured, Gamify can announce levels and trophies to the workspace channel it already uses, so there is one place to configure Telegram for the whole workspace. Penalties are never announced there. ### Rules that need an app you do not have Rules belonging to an app that is not installed are shown in the settings screen marked "Requires " and never fire. Installing the app activates them; you do not need to reconfigure anything.