# App Settings

### **App Configuration​**

#### **General**

The General section contains core settings that affect how the app behaves for end users.

**Language** lets you choose the default language used in the app. If you select Browser's Language, the app will follow the language configured in the user's browser.

**Venue used on initial load** lets you choose which venue is shown first when the app opens. This option is only relevant when your solution contains more than one venue. If no specific venue is selected, the default venue is the first venue in alphabetical order.

**Map Markers Visibility** controls whether map markers are shown on the map. You can choose Default, Show, or Hide. The default behavior follows the map configuration already used by the app.

**Road Names Visibility** is available when using Mapbox map. It controls whether road names are shown on the map. You can choose Default, Show, or Hide.

**Disable Lazy Loading** is available when using Mapbox map. By default, the app loads map data only for the visible part of the map, which improves initial load time. If you disable lazy loading, all map data is loaded up front. This may make the first load slower, but navigation can feel smoother afterwards.

**Remove Mapbox Extruded Buildings** is available when using Mapbox. Enable this option to remove 3D extruded buildings from the map.

**Search External Locations** allows search results to include locations outside your MapsIndoors dataset, such as external addresses and places from third-party providers.

Under **Visibility** options, you can control whether certain UI elements are shown in the app:

* **View Selector** visibility shows or hides the View Selector. This selector is only relevant when more than one building is available.
* **Language Selector** visibility shows or hides the language selector in the app.
* **External Travel Mode Dropdown** visibility shows or hides the travel mode selector for external directions.
* **Full Screen button** visibility shows or hides the full screen button.

**App Title** sets the name of your app as it appears in the application.

**Alias** is a human-readable shortname for your API key — instead of a random string, you can load your solution with a memorable name like `my-company-hq`. Leave this blank if you want to make it harder for others to discover and load your map data.

[**User Roles**](/cms/core-concepts/editor.md) control what locations and wayfinding routes are visible to different groups of users. You can add new roles, and edit the display name of each role (including translations).

**App Categories** lets you control the order and visibility of Categories as they appear in your app's browse menu. Drag categories up and down to reorder them, and toggle the visibility switch to show or hide individual categories in the app.

#### **Map Provider**

The Map Provider section is used to provide the credentials needed for the map service used by the Web App.

**Mapbox Access Token** is used when your app runs with Mapbox.

**Google Maps API** key is used when your app runs with Google Maps.

Enter the relevant token or API key depending on the map provider your solution uses.

#### **Kiosk Controls**

The Kiosk Controls section contains settings specific to kiosk mode.

**Enable accessibility** enables accessibility controls and layout adjustments for kiosk mode.

**Horizontal Categories Enabled** changes the kiosk layout so categories are displayed horizontally instead of vertically.

**Enable kiosk QR Code** controls whether the kiosk QR code is shown. This is enabled by default.

**Enable kiosk step move** allows users to move between steps in kiosk mode. By default, kiosk step movement is disabled.

#### **Mapbox Map Style**

The Mapbox Map Style section is only available when Mapbox is enabled.

Use Mapbox Map Style to provide the style URL used by the Web App. This determines the visual appearance of the Mapbox map.

#### **Styling**

The Styling section lets you customize the visual identity of the app.

**Loading screen logo** lets you choose the logo shown on the loading screen. Click Open Media Library to select an image. If a logo is already assigned, you can remove it again.

**Primary Color** sets the app's primary brand color. The value must be entered as a valid hex color code, for example `#000000` or `#FFF`. You can also reset the color back to the default value.

#### **Initial Load View**

The Initial load view section controls how the map appears when the app is first opened.

**Start Zoom Level** sets the zoom level used when the map loads initially. The allowed range is 0 to 22.

**Min Zoom Level** sets the minimum zoom level users can zoom out to. The allowed range is 1 to 20.

**Bearing** is available when using Mapbox. It controls the rotation of the map. A value of `0` means north is up. The allowed range is 0 to 360.

**Pitch** is available when using Mapbox. It controls the viewing angle of the map. A value of `0` is a top-down view. The allowed range is 0 to 85.

Under Center, you can define the coordinates used to center the map on initial load:

* Latitude must be between -90 and 90.
* Longitude must be between -180 and 180.

Both latitude and longitude must be entered together. If only one value is provided, the configuration is considered invalid.

The "App Title" is used to set a name for your app in your application.

The "Alias" is a shorter name you can use for loading your application in your app. Think of it as a "named API key", so instead of a random combinations of letters and numbers, it's an easy to remember name instead.\ <br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.mapsindoors.com/cms/interface/solution-details-interface/app-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.