Customer Portal & Public Surfaces
Mobile app (PWA)
Use the staff progressive web app for mobile work, tasks, records, and field operations.
Mobile app (PWA)
Mobile app and PWA covers The mobile-friendly staff client and launchpad experience for tasks, module apps, pages, objects, and saved shortcuts. Use this page when you are configuring the live product surface, planning a rollout, or checking why users see different data from what an administrator sees.
What this surface is
- Primary purpose: The mobile-friendly staff client and launchpad experience for tasks, module apps, pages, objects, and saved shortcuts.
- Where staff start: Users open the PWA from the tenant web app; launchpad routes include
/launchpadand/launchpad/dark. - Where admins configure it: Admins control enabled tenant apps, launchpad tiles, page/object shortcuts, and mobile-enabled menu entries.
- Runtime/detail surface: Launchpad tiles are stored in tenant settings and can include app keys plus page or object shortcuts.
- Platform connections: The PWA shares tenant data, roles, menus, and object access with the main web app.
Common workflows
| Workflow | What happens | Where to check |
|---|---|---|
| Enable only | Enable only the module apps that should be available to mobile users | Confirm in the product route above before publishing. |
| Use launchpad | Use launchpad Manage apps to control which tiles appear for staff with permission | Confirm in the product route above before publishing. |
| Create page | Create page and object shortcuts for the highest-volume mobile tasks | Confirm in the product route above before publishing. |
| Mark menu | Mark menu shortcuts as mobile-enabled where they should appear in the PWA grid | Confirm in the product route above before publishing. |
Configure it
- Enable only the module apps that should be available to mobile users.
- Use launchpad Manage apps to control which tiles appear for staff with permission.
- Create page and object shortcuts for the highest-volume mobile tasks.
- Mark menu shortcuts as mobile-enabled where they should appear in the PWA grid.
- Check each shortcut opens a responsive page, object list, or module route.
- Test task, ticket, record, and approval flows on a phone-sized viewport.
- Review login, session timeout, and browser notification settings before rollout.
- Ask a pilot user to complete the most common field workflow end to end.
Configuration options
| Option | Use when | Notes |
|---|---|---|
| App tile | A module should appear in the launchpad | Uses stable keys such as tasks, tickets, projects, or inventory. |
| Page shortcut | A site page should open directly | Eligible shortcuts point to /sites/:slug. |
| Object shortcut | A dynamic object list should open directly | Eligible shortcuts point to /objects/:objectName/list. |
| Dark launchpad | Users prefer the dark launchpad view | Route: /launchpad/dark. |
| Settings tile | Admins need tenant configuration | Route: /global-settings. |
| Browser notifications | Mobile users need alerts | Configure company and notification settings. |
Operating notes
- Mobile pages should avoid dense tables unless filters and cards make them usable.
- Do not assume every desktop page is ready for field work; test with real data volume.
- Launchpad ordering is tenant-wide, while permissions still control what each user can open.
- If a shortcut does not appear, check menu type, enabled state, mobile flag, and eligibility.
- Use object shortcuts for field teams that mainly create or update one record type.
- Keep public/customer portal use cases separate from staff PWA use cases.
- Offline behaviour should not be promised unless the specific route has been tested for it.
- Use shorter labels and icons for mobile launchpad tiles.
- Review session timeout so users are not logged out mid-field operation.
- Publish PWA guidance with screenshots for users who install it to a home screen.
For developers
Use the developer and reference pages when this configuration is read or changed by code, scripts, widgets, embeds, API clients, or webhooks.