MapsIndoors CMS

Last updated:

The MapsIndoors Content Management System (CMS) enables you to add, edit, and maintain your data within the MapsIndoors platform.

Your data is structured in a hierarchy where the top level is your Solution which can contain multiple Venues, which in turn can have multiple Buildings and so on. The data-types in hierarchical order:

  • Solution
    • A Solution is the topmost level of your data structure. It encompasses all of the Venues, Buildings and Locations that you need for your MapsIndoors implementation. It is possible to have more than one Solution, but for the vast majority of use-cases, you will just have one.
  • Venues
    • A Venue is the second level of data. You can have multiple Venues in one Solution. For example, a large company might have multiple offices spread over the country. Each of these could be a Venue, but under the same Solution. A Venue can consist of one or more Buildings. For example, a sports stadium might be many Buildings, but it is all considered the same Venue.
  • Buildings
    • A Building is a collection of Floors. Inside a Venue you can have one or more Buildings and an Outside area. Outside is categorized together with Buildings, because it is a part of what comprises a Venue.
  • Floors
    • Floors are the levels that exist within a Building. A Building has at least one Floor.
  • Locations
    • There are three kinds of Locations: Rooms, Areas, and Points of Interest (POIs).
      • A Room is a multi-point polygon, representing the walls of the physical Room, like a meeting room, or a restroom.

      • A POI is a point on the Map that can be added and moved in the CMS. POIs do not have any polygon data as it consists of only one point. Some examples of POIs are locations that are not available in Floor plan drawings, such as coffee machines, food trucks, or temporary event structures.

View the tutorial video below for more information about terminology and hierarchy, or visit the Glossary.

You can also view the full video tutorial of the CMS:

Or if you're just interested in the general concepts:

There are two main pages in the CMS, "Map" and "Solution Details". The hierarchical structure is like this:

  • Map - The main page where you manage your data on the map.
  • Solution Details - A "behind-the-scenes" page, where you administrate things such as Categories, Types, Visibility, etc.
    • Types - Defines "types" of Locations. Types work as specific identifiers for a group of Locations such as "Canteen", "Bathroom", etc.
    • Categories - Categories are a way to group or organize Locations for easier browsing in your application. Categories can be used to group Locations in bundles regardless of their Type.
    • Type Visibility - Defines the Zoom Levels for which the Locations of each Type will appear on the Map.
    • Buildings - An overview of the Buildings present in your Venue.
    • Venues - An overview of the Venues present in your Solution.
    • App Settings - A page with various settings concerning your app.
      • App Configuration - Settings to configure your app.
      • API Keys - API Keys used by your Solution.
      • Booking Provider - Settings for the booking provider you use for your Solution.
      • Position Provider - Settings for the position provider you use for your Solution.
      • Webex - Settings for your Cisco Webex Integration.

In the CMS there are different levels of users, which has an effect on what you have access to. For example, an "Admin" level user has access to Solution-level settings, whereas an "Editor" primarily has access to create and edit Locations on the Map. This documentation is written with an Admin user level in mind.

  • Administrator - Administrators have full access to all menu points and options shown in the list above.
  • Editor - Editors have more limited access than Administrators, being limited to creating new Locations, alongside editing and deleting existing Locations. This gives you access to the following tools:
    • Add POI - Creates a Point of Interest where you click on the Map. Afterwards it opens an editor where Location details can be adjusted.
    • Add Area - Creates an Area by clicking on the Map to create corners of a polygon. Afterwards it opens an editor where Area details can be adjusted.
    • All Display Filter options.
    • The following Location Editor Options:
      • Type - Locations must have a Type applied, which can be set in the Location details editor. When creating a new Location some settings are inherited from the selected Type e.g. Name and Icon. You can always change the inherited settings to something else if necessary.
      • Name & Description - Type in the name of your Location, and a Description. Entering it in the default language is mandatory, but you also have options to enter it in alternative languages.
      • Categories - Add which, if any, Categories this Location belongs to.
      • External ID - You can define an External ID that a Location should use alongside its internal ID.
      • Area - Choose the rotation of the Area the Location covers.
      • Search - Other search terms that can be searched, and still return this Location, even if it is not a match to the Name, Type or Category.
      • Restrictions - Determine which, if any, App User Role Restrictions this Location should be subject to.
      • Visibility - If your Location is only displayed and searchable for a given time period, you can define that here.
      • Image - Assign an image to be used for this Location.
      • Custom Properties - MapsIndoors supports Custom Properties, defined by key-value pairs.
      • Details - Select which Building and Floor this Location should belong to.

Interface Overview

If you prefer to receive the following information in video format, watch the video below!

Map

The Map section is the main navigation of the MapsIndoors CMS and includes the Filter bar at the top, Toolbar at the bottom, a Floor selector on the right, and your Map in the center.

map-main

  1. Select the active Solution.
  2. Enters the "Map" view (shown on the image). This is the page you see when logging into the CMS.
  3. Enters the "Solution Details" menu containing the submenus mentioned earlier.
  4. Open the Standard Web App using the information entered in the CMS. (Only available if you have set an Alias)
  5. Enter the "Settings" menu page containing subpages.
  6. Opens a drop-down menu containing options such as "Docs", "Log Out", and a link to enabling two-factor authentication.
  7. Select the active Venue. The filter bar can then be used to narrow down the data you see on the Map and Lists for this Venue.
  8. Select one or more Buildings.
  9. Select one or more Floors. This is active when a single Building is selected.
  10. Filters on whether Rooms, POIs, and Areas should be shown on the Map and in the List.
  11. A filter to narrow down Locations to display of specific Location Types.
  12. A filter to narrow down Locations to display of specific Categories.
  13. A filter to narrow down Locations to display with specific App User Roles applied.
  14. Click to search for Locations using a Location’s name, Location ID, Alias, or External ID.
  15. Bulk edit button activated by selecting one or more Locations in the List view. This allows you to bulk update Location Attributes, such as Location Type, Searchability, Categories, Aliases, and more.
  16. Expands a list containing all your Locations. Filters are applied to Location data shown on both the Map and in the List view.
  17. A Floor selector, to select the displayed Floor on the Map.
  18. The main toolbar to modify your Solution.

The below video demonstrates the use of the Filter bar to narrow down search results on the map and in the List view.

Toolbar

map-toolbar

From left to right, the functionalities in the Toolbar are as follows (you can also hover over the icons in the CMS to see their names):

  • Add POI - Creates a Point of Interest where you click on the Map. Afterwards it opens an editor where Location details can be adjusted.
  • Add Area - Creates an Area by clicking on the Map to create corners of a polygon. Afterwards it opens an editor where Area details can be adjusted.
  • Show Network - A toggle button to show or hide the Route Network your Directions feature will use.
  • Add Barrier Route Element - Creates a Route Element on your map. The Barrier Route Element can be used to apply e.g. restrictions, delay, or define one way direction to specific parts of the Network. For example, if you do not want your directions to guide your visitors down a specific hallway, but there isn't a Door present, this Route Element can be used.
  • Reload Route Network - Reloads the Route Network. Route Element changes' effect on the Network becomes visible after reloading the Network.
  • Zoom Level - Adjust the Zoom Level. Values range from 15 (zoom out) to 22 (zoom in).

Doors & Barriers

Doors and Barriers are Route Elements that allow you to manipulate certain portions of the Route Network. They appear if you click the Show Network button mentioned above.

Doors are a Route Element that indicates the presence of a door - or other entryway - in a building.

door-menu

  • Type - Lets you define what type of Door this is. Each type has different defaults.
    • Door - A Door between two Rooms inside the same Building.
    • ElevatorDoor - A Door for an elevator, comes with a built-in Delay.
    • ExternalDoor - A type of Door that links to the outside Route Network, only connects to one Room.
    • InterBuildingDoor - A Door that connects between two Rooms in two different Buildings.
    • Opening - An entryway between two Rooms inside the same Building, but with no physical door.
    • Hatchway - A specific kind of Door that is used for smaller rooms in some specific situations.
  • Restrictions - Set optional restrictions on who can use this Door.
    • Open for all - Open for all Users.
    • Open for specific App User Roles - Define certain App User Roles that can use this Door.
    • Closed for all - No Users can use this door.
  • Delay (seconds) - Set a Delay in seconds for routes that pass through this door. Used in estimated arrival time calculations.
  • Radius (meters) - Set the Radius in meters for this Door, to ensure it touches the Route Network.
  • Floor Index - Use this to move a Door between two Floors.
  • One way direction (bearing) - The exit angle of a one-way Door, in degrees, like a compass bearing. In the illustration below, the entered value would be 45, as the user would exit at a 45 degree bearing.

one-way-bearing

Barriers are similar to Doors in the sense that they are used to modify the Route Network. Many of the settings and restrictions you can set are the same between the two kinds.

barrier-menu

  • Restrictions - Set optional restrictions on who can bypass this Barrier.
    • Open for all - Open for all Users.
    • Open for specific App User Roles - Define certain App User Roles that can bypass this Barrier.
    • Closed for all - No Users can bypass this Barrier.
  • Delay (seconds) - Set a Delay in seconds for routes that pass through this Barrier. Used in estimated arrival time calculations.
  • Radius (meters) - Set the Radius in meters for this Barrier, to ensure it touches the Route Network.
  • Floor Index - Use this to move a Barrier between two Floors.
  • One way direction (bearing) - The exit angle of a one-way Barrier, in degrees, like a compass bearing. In the illustration above, the entered value would be 45, as the user would exit at a 45 degree bearing.

Solution Details

Under Solution Details you can find several subpages, which are described below:

Types

solution-details-types

This page is for organising the "Types" you sort your locations in to.

  1. Create a new Type.
  2. Click to select a Type, for easy selection of multiple Types at once.
  3. "Edit Type" - Gives you the option to change the name of the Type, or to modify the App User Role restrictions.
  4. "Edit Display Rules" - The ability to modify the Display Rules for a given Type. Read more about Display Rules.
  5. The name of the Type.
  6. The Icon assigned to the Type.
  7. Displays what information the Type's Label contains when displayed on your Map.
  8. The number of Locations with the given Type applied.
  9. "Edit Template" - Edit the template for a given Type.

Categories

solution-details-categories

Categories are similar to Types, but whereas Locations can only be of one Type, they can be of multiple Categories. Categories are used for browsing important Locations, or amenities, in your application. - For example, a canteen might be in a Category of both "Food" and "Leisure", but still only be of the Type "Canteen".

  1. Create a new Category.
  2. "Edit Category" - Edit properties of your Category.
  3. The name of the Category.
  4. The Key belonging to the Category.

Type Visibility

solution-details-type-visibility

Type Visibility is the term used to determine at which Zoom Levels both the Types' Icons and Labels are visible.

  1. A save button. Click this to save your changes.
  2. Visibility toggle - Click to toggle on/off the Type visibility. It controls whether the Type Icons and Labels are shown on the Map
  3. Set the minimum and maximum Zoom Level at which a given Type should be visible.

Buildings

solution-details-buildings

This page provides you with a list of the Buildings in the selected Venue in your Solution.

  1. "Edit Building". Lets you edit the properties of the Building, such as name, ID and Floors.
  2. The Name of the Building.
  3. The Administrative ID of the Building.
  4. The Address of the Building.

Venues

solution-details-venues

A page featuring a list of Venues in your Solution. These are provided by MapsIndoors, and to add more, contact your representative.

  1. "Edit Venue" - You can e.g. edit Venue Name and Venue External ID in the Venue details editor.
  2. The Name of your Venues.
  3. The Venue ID of your Venue.

App Settings

This page contains various subpages with more advanced settings about your app.

App Configuration

This page contains various settings, such as names for your API keys, App User Roles and App Categories.

solution-details-app-title

Here you can change the title of your app.

  1. Save the changes you've made.
  2. Enter the name you wish to use.

solution-details-alias

The API Keys used to make your MapsIndoors Solution consist of random combinations of letters and numbers. Here, you can assign them an Alias to make it easier to remember.

NOTE: Do not set an Alias if you want to make it more difficult to find and load your MapsIndoors data. In that case, you should only load the data with an API key.

solution-details-app-user-roles

You can also modify your App User Roles from within these pages.

  1. "Edit Role" - Edit settings pertaining to one specific App User Role.
  2. The names of your App User Roles.
  3. "Add App User Role" - Create a new App User Role.

solution-details-app-categories

Here you can select which Categories can be used for browsing the app.

  1. Move your app Categories up and down in order.
  2. The name of the Category.
  3. Toggle whether or not the Category in question is visible in the app.
  4. The Icon selected for the Category.
  5. Select an Icon to be used for the Category.
API Keys

Here you manage the active API keys generated for your Solution. To load your MapsIndoors data in your apps, you need an API key.

You can create as many API keys as you want, and it is good practise to use one for each place you need to load data from MapsIndoors (each mobile platform, web app etc.).

You can easily delete an API key if it is unused, or has been compromised in some way.

solution-details-api-keys

  1. The name that you want to use to identify the new API key.
  2. Generate API key.
  3. The name of an active API key.
  4. Save any changes you make.
  5. Toggle between active and inactive API keys.
  6. Your API key is located here in text form.
  7. Delete the API key.
Booking Provider

This submenu presents you the option of integrating a Booking system to your Solution. The exact menus presented here depend on which provider you opt for.

Position Provider

MapsIndoors also provides you the option of integrating a Positioning system to your Solution. The exact menus presented here, like the Booking system, depend on which provider you opt for.

Webex

As the options above, the options presented for WebEx integration depends on the exact manner of integration.

Editing Data

Location

Each Location also has a number of settings associated with it. If you select a Location on the Map or in the List view in the CMS, you will be presented with a modal with the following settings:

  • Type - Locations must have a Type applied, which can be set in the Location details editor. When creating a new Location some settings are inherited from the selected Type e.g. Name and Icon. You can always change the inherited settings to something else if necessary.
  • Name & Description - Type in the name of your Location, and a Description. Entering it in the default language is mandatory, but you also have options to enter it in alternative languages.
  • Area - Choose the colour of the Area the Location covers. You can also set whether the Area is visible or not.
  • Status - Toggle whether or not this Location appears in searches.
  • Restrictions - Determine which, if any, App User Role Restrictions this Location should be subject to.
  • Categories - Add which, if any, Categories this Location belongs to.
  • Location Icon - You can set an Icon to be used on the Map for this Location.
  • Image Options - Here you have the option to connect an image to a Location. See below for further details.
  • Search Aliases - Other search terms that can be searched, and still return this Location, even if it is not a match to the Name, Type or Category.
  • Venue Details - Select which Building and Floor this Location should belong to.
  • External ID - You can define an External ID that a Location should use alongside its internal ID.
  • Coordinates - The coordinates of your Location.
  • MapsIndoors Location ID - The internal ID of your Location.
  • Active - If your Location is only displayed and searchable for a given time period, you can define that here.
  • Custom Properties - MapsIndoors supports Custom Properties, defined by key-value pairs.
  • Location History - See the editing history of this Location.

Image Options with IndoorView

IndoorView is only supported for web

To get started using the IndoorView feature for your Locations, please make sure that the Google Street View panorama images are publicly available for your building by looking at Google Maps. If no imagery is available, please contact a certified Street View Photographer.

  1. Click "Set Street View image”

    • This will open a Google Street View window showing the image closest to this Location. Please note that the MapsIndoors CMS looks for panorama images within a certain radius from the Location's position, so make sure to have panorama images published in that area.
  2. Navigate Street View and find an image and viewing angle that is suitable

  3. Click "Set image”

Mapsindoors Support Matrix
MapsIndoors Support for IndoorView Private hosted panorama images
CMS Yes No
Web App Yes No
Android App No No
iOS App No No
Web SDK Yes, through Google Maps Street View API or Static Street View API No
Android SDK No No
iOS SDK No No

IndoorView only supports publicly available Google Street View imagery. If you would like to know more about privately hosted panorama images, please see Googles Custom Street View documentation.

Developing Your Own App

When developing your own app, you can still use the MapsIndoors CMS to save the Google Street View image information to a Location. When the Panorama image is set, the Location gets populated with a streetViewConfig property. Please see below for an example.

Location Object:

{
"id": "586ce41ebc1f571794b9e924",
...
"properties": {
"name": "Copenhagen",
...
"streetViewConfig": {
"panoramaId": "CAoSLEFGMVFpcE41dTZnVzNpVnU1WmliRjk0T2tpMENhZ3Fya3ljVFh3TjVzN2lY",
"povHeading": 203.1294893976259,
"povPitch": -13.068754012666432
}
}
}

The parameters above can be used to show a static Street View image through the Street View Static API. Please see the Street View documentation for more information.

A Street View panorama image can be initialized in a <div> the following way:

function initStreetView(streetViewConfig) {
const panorama = new google.maps.StreetViewPanorama(
document.getElementById('panorama'),
{
pano: streetViewConfig.panoramaId,
pov: {
heading: streetViewConfig.povHeading,
pitch: streetViewConfig.povPitch
},
zoom: 0,
visible: true
});
}

Please see the official Google Street View Service documentation for more information.

2D Models and Icons

The Media Library currently supports 2D models and Icons.

In the CMS you can change the Icons for markers on the Map by using the Media Library. This is done by opening the Media Library from the Icon and 2D model sections in the Display Rules editor, both on Location and Type level. More information about the Media Library can be found here.

In the Media Library, you can see and manage all uploaded media, both 2D models and icons. Media can be either in .jpg, .png or .svg file formats. For icons specifically, we highly recommend using the SVG format.

Icons have a suggested limit of 128x64 pixels, and no more than 150kb in size, but this can be overridden. There is a hard limit on file size of 8 mb.

Please note, that when using the Integration API, all Media must reside on a server that has CORS enabled. Otherwise the Media can't be loaded when using the JavaScript SDK.

If your images appear "too large" on the map, please revisit your settings.

Uploading SVGs

SVG is a vector file format, which lets MapsIndoors convert your Icon in a range of sizes to get the best looking Icon in every situation.

SVGs should be uploaded with a width and height that you want the SVG to be displayed on the Map in. Make sure you define it in px, not cm or %. E.g., if you want to display a 32x24px Icon on the Map, upload an SVG with the attributes width='32px' and height='24px'. For consistency, it's good form to make the viewport the same size as the width and height.

Supported SVG Elements

We only accept SVGs that conform to a very strict ruleset. If an uploaded SVG contains anything other than the elements and attributes listed below, it will be rejected. All child elements can be nested as supported by the SVG format.

  • <svg> element
  • viewbox attribute
  • <path> child element
  • <rect> child element
  • <title> child element
  • <desc> child element
  • <circle> child element
  • <defs> child element
  • <ellipse> child element
  • <line> child element
  • <pattern> child element
  • <polygon> child element
  • <polyline> child element
  • <text> child element
  • <stop> child element
  • <use> child element
  • <linearGradient> child element
  • <radialGradient> child element
  • <symbol> child element
  • <style> child element
  • <tspan> child element

When you try to upload an SVG containing one or more of these elements and/or attributes, the upload is cancelled and you will see which files contain the unsupported elements.

If your SVGs contain unsupported elements, you must remove them before they can be uploaded. One typical issue is embedded base64 data in the SVG, which usually indicates the SVG will display raster image data (PNGs and the like) somewhere in it. That can lead to unintended consequences on the map.

SVG Help

Michelle Barker has written a terrific guide to optimizing SVGs for the web on her site.

A great tool to strip unnecesary elements from your SVG-file is SVGOMG by Jake Archibald.

Syncing Icons to Other Solutions

If you have multiple Solutions, you can sync Media across multiple Solutions to make sure you can use the same Media in all of your Solutions.

Open the Media Library. Find the Media you want to sync to one or more Solutions, and click the "Sync"-icon. Then you can select which other Solutions you want to sync this Media to.

When you sync a piece of Media, if the Media exists in the target Solution (i.e. a piece of Media with the exact same filename), you override the Media in the target Solution. If the Media does not exist in the target Solution, it is added.

PNG Image File Support

We highly recommend using SVGs for Icons across MapsIndoors, but support PNG files as well.

When uploading an Icon in the PNG format, make sure you upload it in a 3x size to accommodate for it being scaled down on the map. For example, to display a 20x20px Icon on the Map, upload it in 60x60px.

Split and Combine

This is a paid feature. Contact us to learn more!

Split and Combine are features that enable you to edit a Room's geometry. A Room can either be split in two, or combined with another Room.

The Split and Combine features are useful if you want to make quick changes to your Rooms. If you want to make groundbreaking changes to a Floor or Building layout, reach out to your contact at MapsPeople with your updated CAD drawings.

One use case for Split and Combine is to manage the layout of an exhibition for a temporary event in a convention center. Combine booths or split them into smaller ones based on the event demands.

Another use case is if you make changes to your office layout without making any structural changes to the building. E.g. you might knock down a plaster wall to combine two meeting rooms or the like, which doesn’t necessarily require a full redrawing of your floor layout by our team of specialists.

How to split

Select a Room on the map. In the Location Details editor, click on the “Split”-button. Place two points on the borders of the Rooms where you'd like to split it. Then choose which Room is the new Room on the map. The new Room will get a new ID, but otherwise copy all other data from the original Room. The old Room will retain all of the original data.

You can get a helping hand after placing the first splitting point by holding down the "Shift" key on your keyboard. The line will be drawn perpendicular (at a 90° angle) to the Room's wall.

If you exit the Split mode before completing the split, your changes will be discarded.

Detailed constraints for Split

  1. The split must contain two points touching the edge/Walls of the Room.
  2. The split can not extend outside of the Room.
  3. The split must not intersect with any holes in the Room.
  4. The split must be at least 1 meter from any Walls or holes.
  5. The outcome of the split must be at least 1 square meters in size.
  6. A split must not overlap itself.

How to combine

Select a Room on the map. In the Location Details editor, click on the “Combine”-button.

The selected Room is now highlighted on the map, with the compatible Rooms highlighted in a different color. Click on the other Room you'd like to combine with your selected Room.

The combined Room’s Location Details are based on the first selected Room’s Location Details. If you have any external integrations that rely on a Room's ID, make sure the Rooms are selected in the right order.

If you exit the Combine mode before completing the combination, your changes will be discarded.

Detailed constraints for Combine

  1. All Locations must be of the same Type.
  2. The Rooms must share at least 1 meter of unbroken Wall.

Settings

Logs

The Audit Log functionality is a configurable feature in MapsIndoors and if not enabled on your Solution it can be on request.

The Audit Log feature can be used to access the Audit log on MapsIndoor data objects, i.e. you can find or inspect the change history.

The Log functionality is found in the Logs tab under Settings in the CMS.

The Log can be filtered on date, ID, User and Data object types. When pressing download a comma separated file (csv) will be stored on your computer's hard drive.

The log will be in CSV format, which can be opened by a spreadsheet program eg. Excel. Each log entry represents a modification in the data. In short, each entry tells at what time who did what to which object.

The headers represented are: Time, User, Action, ObjectType, ObjectId and ObjectData

  • Time: Tells which user did the change (The email representing the user logged in to the system)
  • Action: Tells what happened:
    • If data was added, the 'Action' will be set to 'Created'
    • If data was changed, the 'Action' will be set to 'Changed'
    • If data was deleted, the 'Action' will be set to 'Deleted'
  • ObjectType: Tells what type of data was modified (eg. ‘building', ‘location', ‘user', ‘graphdata' ... )
  • ObjectId: Is a unique ID that represents the given data - Building, Location or whatever it is.
  • ObjectData: Is a JSON formatted representation of the actual data stored in the MapsIndoors system. To see what changed you can compare this data to the previous change.

Examples of use cases could be:

  • How to do I get Network history? Filter the ObjectType to ‘graphdata' to see these entries. To find a particular user history, filter ‘User' to their email as well.
  • How to do I get Categories history? Filter the ObjectType to ‘category' to see these entries. To find a particular data history, filter ‘User' to their email as well.
  • How to do I get Location Type/type template/visibility history? Filter the ObjectType to ‘locationtype' to see these entries. To find a particular data history, filter ‘User' to their email as well. The type template is covered in the "LocationTypeField” section of the data. The visibility is covered in the "displayrule” section of the data
  • How to find user login activity? When a user logs in, the corresponding user object will be changed too (the ‘last login field will be updated'). Filter the ObjectType to ‘user' to see login entries. To find a particular user login history, filter ‘User' to their email as well.

If you use Excel you can find a video on how to open a CSV file here: https://www.youtube.com/watch?v=z5Pxil4jVO4

  • Icons: Icons are used for various Locations on the map, e.g. POIs, Rooms. Having a unified representation for specific types of Locations makes the system easier for users to engage with.
  • Location: A term used for all Rooms and Points of Interest (POI).
  • POI: "Point of interest” - is usually an object that isn't tied to a Room. E.g. Vending Machine, Locker, A Statue, ATM etc.
  • Type: All Locations are of a Type. Types serve as templates for Locations to provide a basic setup. Many of the properties can later be overridden for specific Locations.
  • Venue: Typically a collection of Buildings that are close geographically.
  • Search alias: An alternative name for a Location allowing users to search for the Location by that name.

Users

Allows Admins to control who has access, and what roles they have, as well as create new users.

A list appears with all users for the Solution. You can also search for an email via the search box in the upper right.

Editing a user: Click on the pencil to the left of the email. The user can be deleted, changed role or added to a Solution. Click Save.

New user: Click on new user bottom at top. Enter email, choose Editor or Administrator, and assign the appropriate Solution. Click Create.

Support

Something not working?

If you have found a bug or encountered an issue you can not resolve, please reach out through our support portal.

Feedback

Do you have feedback for us?

Send us an email at cms-feedback@mapspeople.com