> For the complete documentation index, see [llms.txt](https://docs.mapsindoors.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mapsindoors.com/cms/interface/solution-details-interface/solution-settings.md).

# Solution Settings

Solution Settings contains advanced styling and behavior configuration that applies across your entire solution.

Navigate here via **Solution Details → Solution Settings**.

***

### Main Display Rule

The Main Display Rule sets the default appearance for every location on your map. Think of it as the master style template — individual Location Types and locations can override specific values, but anything not overridden will look exactly as you've set it here.

<figure><img src="https://393726209-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fr7ggkwTwz3UJfNWm5Mwk%2Fuploads%2Fgit-blob-ae816a9ddf9bacefadcb8446cab71e3bcb762c75%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

The editor is divided into sections: **General**, **Icon**, **Label**, **Polygon**, **Extrusion**, **2D Model**, and **3D Model**. Changes you make here instantly become the new default across your entire solution.

For a full walkthrough of all the options, see [Display Rules](https://docs.mapsindoors.com/cms/core-concepts/display-rules.md).

***

### Building Highlight

Building Highlight controls the colored outline drawn around your buildings on the map — useful for making buildings stand out from the surrounding area.

<figure><img src="https://393726209-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fr7ggkwTwz3UJfNWm5Mwk%2Fuploads%2Fgit-blob-533223a956d5ad9ad144a21f088d8a1cffae6511%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

| Setting            | Description                                                                                                |
| ------------------ | ---------------------------------------------------------------------------------------------------------- |
| **Visibility**     | Show or hide the building outline.                                                                         |
| **Zoom from**      | The zoom level at which the outline starts appearing.                                                      |
| **Zoom to**        | The zoom level at which the outline stops appearing. Check **Max zoom** to keep it visible all the way in. |
| **Stroke color**   | The color of the outline. Click the color picker to choose.                                                |
| **Stroke width**   | How thick the outline appears, in pixels.                                                                  |
| **Stroke opacity** | How transparent the outline is, from `0` (invisible) to `1` (fully visible).                               |

**Zoom from** and **Zoom to** accept a number between `1` (very far out) and `25` (very close). Zoom level 25 is not available for all Solutions. Most Solutions only need values between 15 and 25. Checking **Max zoom** keeps the outline visible at the largest possible zoom level; this value may increase in the future.

{% hint style="info" %}
**Note:** The JavaScript SDK for Google Maps requires whole-number zoom levels. On Android and iOS, and with other map providers, the value may be fractional.
{% endhint %}

If you set the outline color in app code instead of in the CMS, use a 6-digit HEX value, for example `#3071D9`.

***

### Map Behavior

Map Behavior controls whether locations on your map are clickable by default.

<figure><img src="https://393726209-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fr7ggkwTwz3UJfNWm5Mwk%2Fuploads%2Fgit-blob-4eba2e3587036f0ad0a02d4f32776bb2e2d5ebb6%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

When **Selectable** is turned on, users can tap or click locations to see their details. Turn it off if you want a browsable map where clicking locations does nothing — useful for display screens or kiosk setups where you don't want users navigating into location detail views. This default can still be overridden for individual Types or locations.

{% hint style="info" %}
**Note:** Clustering and Collision Handling are currently not respected by the Web SDK.
{% endhint %}

#### Icon zoom scaling

On Solutions that use Mapbox, the **Icon zoom scaling** section lets Icons grow as users zoom in. Turn on **Enable Icon zoom scaling** and set **Scale from zoom level** and **Scale to zoom level**. Both must be between `1` and `24`, and **Scale to zoom level** must be larger than **Scale from zoom level**. How much each Icon grows is set with **Zoom scaling** in the Icon section of the Display Rule editor. See [Icon Zoom Scaling](https://docs.mapsindoors.com/cms/core-concepts/display-rules/icon-zoom-scaling.md).

***

### 3D Settings

3D Settings let you control how transparent your 3D walls and room shapes appear across the whole solution.

<figure><img src="https://393726209-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fr7ggkwTwz3UJfNWm5Mwk%2Fuploads%2Fgit-blob-de381818e462568444a107b4da8380b875f77a07%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

**Wall opacity** controls how see-through the 3D walls are.

**Extrusion opacity** does the same for extruded room shapes.

Both use a scale from `0` (completely transparent) to `1` (fully solid).

> **Note:** 3D features require Mapbox and must be enabled for your solution.

***

### Directions Renderer

Directions Renderer controls how a calculated route looks on the map: the route line, its halo and animation, direction arrows, stop icons, floor-change (connector) icons, and start and end markers. The styling applies to every app built on the Solution without code changes.

See [Directions Renderer](https://docs.mapsindoors.com/cms/interface/solution-details-interface/solution-settings/directions-renderer.md) for all settings, defaults, and ranges.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
