When launching the POS app, the merchant-level default app config is initially loaded. Users can override this with tokens before login, but associate or role-level configs in CMS take precedence post-login, ensuring personalized settings. This allows for flexible and tailored app configurations, enhancing user experience and operational efficiency.
Loading App Configs in POS App
When the POS app is first launched, before any associate login, the merchant-level default app config is loaded for the device type the app is running on. After login, if the authenticated user has an associate-level app config defined in CMS, then that app config is loaded. If not, then the system checks if that user’s role has a role-level app config defined in CMS; if so, then that app config is loaded. Lastly, if the user has neither an associate-level app config nor a role-level app config defined in CMS, then the app config applied prior to login is retained (which will typically be the merchant-level default).
Overriding Defaults
When the POS app first launches, it’s possible to override the merchant-level default app config, by using tokens. Restart your app and you'll see the POS app login page. Tap 5 - 10 times in the top right of the screen until a popup launches.
Toggle the environment to PROD or STAGE (see note below for using dev environment). Enter the token and tap Apply. To reset, simply tap Reset.