---
schema_version: "1"
id: 7de91e893dca063e0bf3cedd72954b10f141e657bc06a8f1dd80a7a111aba36b
title: POS App Flow for the Traditional Method for App Config Segmentation
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/commerce/264-0-0/rt_cms_layouts_configs_segments_trad_pos_flow.md
canonical_url: https://help.salesforce.com/s/articleView?id=commerce.rt_cms_layouts_configs_segments_trad_pos_flow.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 296ac0516adda3946ba97e74d16341d9d5ea8a3e53ada857ca63c1feaa7e6719
description: 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.
products:
  - Commerce
release: "264"
---
# POS App Flow for the Traditional Method for App Config Segmentation

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.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/images/icon_note.png)

Note On login, if the user or user’s role has a default app config defined in CMS, then that will override the token-based config loaded before login.

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**.