When a user to logs in to a station from a browser on a mobile device or a PC, the station detects the type of device and uses the appropriate profile, which is assigned to the User Name:
For example, if connecting from a browser running on a laptop PC, the Nav File and Default Web Profile affect: the initial page display, navigation, and display options. If logging in from a mobile phone, the Mobile Nav File and Mobile Web Profile affect the initial view and navigation options.
As a convenience, the Default Mobile Web profile is also available from the Default Web Profile property options for working with mobile views on your PC browser.
The Default Mobile Web profile includes three mobile themes to choose from. Each theme has a set of configurable display options:
These properties are described in Common Mobile interface controls and indicators

The Mobile Nav File is used only to designate a user’s landing page for login (and Home page designation). The user Nav File is used to configure navigation links. Typically, you create the Nav file and then assign the file to a user. The Nav file assigned to the user’s profile determines the initial targeted component for that user. The actual view may depend on user permissions and category settings for the views assigned to that component.
User access to individual mobile views is controlled by the standard NiagaraAX security model of: Users, Permissions, and Categories. So, by default, you must have at least “operator read” permission on an app, or a specific view in that app to see the view. However, if you are designing an app and you want to specify different views for different users, you can use a combination of alternate Px views and permissions to designate the view that a particular user sees. For more details about NiagaraAX security features, see the “Security” chapter in the NiagaraAX User Guide.