# Location Details Editor *** ### Opening the Editor Click any location on the map or select one from the List View. The Location Details Editor will appear as a panel on the **left side** of the screen. The editor is divided into tabs along the left side. Each tab covers a different aspect of the location. Click a tab to navigate to it — your changes are saved per section using the **Save** button. > **Tip:** When you create a new location, some fields are pre-filled based on the Location Type you select — such as the icon and display rules. You can always override these for the individual location.

Location Details Editor Sections (1-4)

*** ### 1. General The General tab covers the core identity of a location. **Location Type** Every location must have a Type — for example, "Meeting Room", "Restroom", or "Canteen". The Type determines default display rules and restrictions that the location inherits. You can change the Type at any time. **Name** The display name of the location. Entering a name in the default language is required. If your solution supports multiple languages, you can add translations using the language tabs (e.g. `en`, `es`). **Description** An optional longer description of the location. Supports multiple languages in the same way as the Name field. **Categories** Assign one or more Categories to the location. Unlike Location Type, a location can belong to multiple Categories at once. Categories are used to group locations for browsing in your app — for example, "Food", "Accessibility", or "Leisure". Categories are managed in Solution Details. **External ID** An optional ID used to link this location to a record in an external system — for example, a facilities management platform or a room booking system. Useful when syncing data between MapsIndoors and third-party tools via the Integration API. > **Tip:** For Mapbox map providers, use spaces to separate words on the same line and press Enter to add a line break in the label shown on the map. **Additional Location Details** Add structured contact and information details to a location — such as a website, phone number, email, or opening hours. These appear as action buttons in the MapsIndoors Web App and Map Template when a user views the location.
Configuring Additional Location Details Four detail types are supported: * **Link** — A clickable URL that opens in a new tab * **Phone Number** * **E-mail** * **Opening Hours** — Structured opening hours for the location
Additional location details in the CMS

Additional location details in the CMS

Each detail entry has the following fields: **URL / Value** — The actual link, phone number, email address, or hours being stored. **Display Text** — The label shown to users instead of the raw value. For example, show "Visit our website" instead of the full URL, or "Call us" instead of the phone number. **Show in App** — Toggle whether this detail appears in the MapsIndoors Web App and Map Template. Useful for storing data you want accessible via the SDK without showing it in the app UI.
Link Additional Detail form in the CMS

Link Additional Detail form in the CMS

**Display Icon** — An icon shown alongside the display text in the app. **Detail Key** — A unique identifier for this detail within the location's data. The key can only be set during initial creation and cannot be changed afterwards — choose it carefully. > **Tip:** The order in which Additional Details appear in the app matches the order they appear in the CMS. Use the up and down arrows next to each entry to reorder them.
Multiple Additional Details that will be shown as Contact Action Buttons in the map template

Multiple Additional Details that will be shown as Contact Action Buttons in the map template

*** ### 2. Selectable Controls whether users can click on this location in the app. * **Selectable** — The location is clickable. Users can tap or click it to see its details. * **Not Selectable** — The location is visible on the map but cannot be clicked. * **Inherit from Type** — The location follows the Selectable setting defined on its Location Type. > **Tip:** Use "Not Selectable" for decorative or structural elements that you want visible on the map but don't need to be interactive — for example, structural columns or decorative areas. *** ### 3. Restrictions Controls which users can see and access this location, based on App User Roles. * **Open for all** — All users can see and access this location. * **Open for specific App User Roles** — Only users with the selected roles can access this location. * **Closed for all** — No users can access this location. * **Inherit from Type** — The location follows the Restrictions set on its Location Type. App User Roles are configured in Solution Settings. *** ### 4. Search Controls how the location behaves in search. **Search Status** Toggle whether the location appears in search results. Turning this off hides the location from all searches in the app without removing it from the map. **Search Aliases** Add alternative search terms that will return this location even if they don't match the name, type, or category. For example, a "Cafeteria" location might have aliases like "lunch", "food", or "canteen". **Active To / From** Set a date range during which the location is displayed and searchable. Useful for temporary locations, seasonal spaces, or event-specific setups. ***

Location Details Editor Sections (5-8)

*** ### 5. Visibility Controls the visual appearance of the location on the map. This tab links directly to the location's Display Rules, where you can override the defaults inherited from the Location Type. Changes made here apply only to this individual location — they do not affect other locations of the same Type. *** ### 6. Image Add a photo to represent this location in the app. This is distinct from the icon used on the map — it should be a real photo of the space, not a pictogram. You can either: * **Select from the Media Library** — choose an image you've already uploaded * **Set a URL** — link to an image hosted externally Images are displayed in the app when a user taps on a location to view its details. *** ### 7. Custom Properties Add key-value pairs to store additional data on a location that isn't covered by the standard fields. Custom properties are accessible through the MapsIndoors SDKs, making them useful for passing custom data into your app logic. Examples of custom property use cases: * Desk booking status * Room capacity * Contact information * Department or team name *** ### 8. Details The Details tab shows read-only system information about the location. **Venue Details** The Building and Floor this location belongs to. **MapsIndoors Location ID** The internal unique ID for this location, used for programmatic references. **Coordinates** The geographic coordinates of the location. **IndoorView (Google Street View)** If your solution uses the JavaScript SDK, you can link a Google Street View panorama image to this location. The CMS will search for available Street View imagery near the location's coordinates. Once set, the location's data will include a `streetViewConfig` property with the panorama ID and viewing angle. > **Note:** IndoorView is only supported for implementations using the JavaScript SDK. Street View panorama images must be publicly available for your building on Google Maps. --- # 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/edit/location-details-editor.md?ask= ``` 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.