Powerups
Optional Whagons modules for specialized operational work.
Powerups extend Whagons beyond the core workspace and task system. Each tenant enables only the modules relevant to its operation, so two customers may have a very different navigation menu while sharing the same task foundation.
Common powerup families
| Family | Examples | Typical use |
|---|---|---|
| Planning | Scheduling, workplans, working hours, time off | Coordinate shifts, capacity, and planned work. |
| Knowledge and compliance | Standards, SOPs, documents, training | Publish procedures, train teams, and review compliance. |
| Assets and inventory | Assets, tools, QR codes, NFC | Track equipment, custody, location, and scan-driven actions. |
| Commercial operations | Purchasing, suppliers, costs, budgets, CRM | Connect operational work to vendors, requests, and spend. |
| Communication | Broadcasts, boards, messages | Coordinate teams outside a single task thread. |
| Insight | Activity, analytics, KPI cards, gamification, goals | Measure throughput, outcomes, and engagement. |
| Vertical operations | Cleaning, operations manager, industry-specific modules | Support specialized frontline workflows. |
| Workbench | Write, Grid, Present | Create collaborative documents, spreadsheets, and presentations. |
How powerups connect to core work
Powerups can introduce their own pages and records, but they normally reuse tenant identity, teams, spots, permissions, and tasks. A purchasing request might create approval work. A training module can use teams and assignments. An asset scan can open a task tied to a location.
Availability
A powerup may be:
- disabled for the tenant;
- available only to certain roles;
- enabled but not yet configured;
- white-labeled or renamed for the organization;
- in a staged rollout.
If a page described here is not visible, check with a tenant administrator before assuming it is missing.
API coverage
The current public v1 API focuses on tenant reference data and tasks. Powerup-specific REST endpoints are not implied by the presence of a product module. Check the API reference for the supported external surface.