Appmint Mobile separates device presentation, staff identity and shared business configuration.
Video tutorials for this topic
Setting ownership
| Setting | Scope |
|---|---|
| Home groups, individual apps and role layout | This device |
| Prep station selection | This device and workflow |
| Show Send to prep, enabled tenders and payment display names | This device |
| Business-location assignment | This device's operating context |
| Printer default, transport and paper width | This device |
| Saved scanner, payment reader and NFC reader | This device |
| Staff roles, permissions, passcodes and registered access cards | Organization |
| Business locations and their addresses | Organization |
| Products, menus, day-parts and availability | Organization and location |
| Event types, scan points, benefits and access rules | Organization and event |
| Workflows, payment gateways and message templates | Organization |
A replacement tablet needs its workstation settings and local hardware connections established. It then uses the shared business records available to the signed-in staff member.
Closing the app and signing out
Returning to an existing app session reuses saved hardware associations and attempts reconnection. A sleeping device should be powered on and kept within range.
Signing out clears account-sensitive local state, including the selected business location and saved peripheral associations. The remembered organization, saved-account entries, Home layout preferences and saved prep-station selections are retained. After a change of organization, review the location and hardware before beginning work.
Deleting the app or clearing its storage requires the workstation to be set up again.
Account security and shared data
The active session uses platform secure storage for authentication tokens. Staff permissions remain enforced for the current account regardless of which tiles the device shows. Saved accounts are a sign-in convenience, not a substitute for the organization's shared-device policy.
Operational data is synchronized through the server. Local carts and pending checkout information support the current working session; they do not replace a saved order or confirmed payment. Save work before handing it to another device, and use the same order when continuing an interrupted payment.
See Layouts, Shared devices and Hardware.
