Skip to content

Hello, How can we help?

Back to FAQ

Understanding the IMPACT mobile app

Last updated: 7 May 2026


What this does

Explains what users can do in the IMPACT mobile app and how it differs from impact-web.

Current access and functionality

  • Verified against the current impact-client, impact-web, and impact-marketplace code on 2026-05-07.
  • impact-client is the mobile app for day-to-day work. It supports personal landing/home views, workspace browsing, tasks, checklists, projects, surveys, members, notifications, settings, marketplace inventory, and selected performance views.
  • Administrative setup remains web-first. Creating company-wide configuration, managing deep workspace settings, subscription administration, and some advanced project setup should be done in impact-web.
  • Mobile access is role-, permission-, feature-flag-, entitlement-, workspace-, and assignment-aware. If a tile or action is missing, the user may not have permission, entitlement, or the feature may be disabled.
  • The app supports local storage and background sync for selected task/checklist/survey activity. Users should still reconnect before assuming changes are fully visible to others.

Main areas

  • Landing / Home - personal work summary, quick action tiles, bookmarked projects, surveys, notifications, and optional custom home cards.
  • Projects - assigned projects, project details, tasks, milestones/phases, risks, documents, surveys, dashboards, and Gantt-style planning where available.
  • Tasks - assigned task workflow, Action / Verify / Accept stages, comments, attachments, status changes, and checklist work.
  • Checklists - assigned task checklists, workspace checklist references, checklist results, file/image inputs, and offline result syncing.
  • Surveys - assigned surveys, survey campaigns, questionnaire responses, and mobile-friendly respondent flows.
  • Marketplace - browsing, item details, owned inventory, orders, and importing supported marketplace content into mobile-supported flows.
  • Settings - language, theme, password/authentication, environment options where enabled, logout, and account actions.

When to use web instead

  • Use impact-web for workspace administration, subscription and entitlement management, company settings, bulk setup, and advanced configuration.
  • Use impact-web when a mobile action is visible as read-only or the mobile app does not expose the create/edit flow.
  • Use impact-web to confirm access issues that depend on workspace ownership, admin permissions, or purchased entitlements.

Common issues

  • Issue: A mobile tile is missing. Fix: Check selected workspace, role permission, feature flags, and subscription entitlement.
  • Issue: A staff user can view information but cannot edit it. Fix: Mobile respects the same permission model as web; some setup actions are admin-only or web-first.
  • Issue: Offline changes are not visible to teammates yet. Fix: Reconnect, leave the app open long enough for sync, and refresh the affected task or checklist.