# User Roles

***

### Administrator vs Editor

|                                                                | Administrator | Editor |
| -------------------------------------------------------------- | ------------- | ------ |
| Create, edit, and delete Locations                             | ✓             | ✓      |
| Use display filters on the map                                 | ✓             | ✓      |
| Access Solution Details (Types, Categories, Buildings, Venues) | ✓             | ✗      |
| Edit Display Rules                                             | ✓             | ✗      |
| Manage Solution Settings and Main Display Rule                 | ✓             | ✗      |
| Access the Media Library                                       | ✓             | ✗      |
| Manage integrations and API keys                               | ✓             | ✗      |
| View and manage CMS users                                      | ✓             | ✗      |
| Access the Audit Log                                           | ✓             | ✗      |

> **Note:** The MapsIndoors documentation is written with Administrator access in mind. Some features described in the docs may not be visible or available if you are logged in as an Editor.

***

### What Administrators can do

Administrators have full access to everything in the CMS. This includes all of the map editing capabilities that Editors have, plus:

* **Solution Details** — manage Location Types, Categories, Buildings, Venues, and App Settings
* **Display Rules** — edit the Main Display Rule and Type-level Display Rules across the entire Solution
* **Solution Settings** — configure solution-wide defaults including the Main Display Rule and Building Highlight
* **Media Library** — upload and manage icons, images, and 3D models
* **Integrations** — manage API keys, Live Data integrations, and other connected services
* **Settings** — manage CMS users and access the Audit Log

***

### What Editors can do

Editors can work directly on the map — creating, editing, and deleting Locations (POIs, Rooms, and Areas). Within the Location editor, Editors have access to all standard fields: Type, Name & Description, Categories, External ID, Search aliases, Restrictions, Visibility, Image, Custom Properties, and Floor/Building assignment.

Editors can also use all display filters on the map to narrow down which Locations they are working with.

What Editors cannot do is access anything outside of the map editing view — Solution Details, Display Rules, Settings, and Solution-level configuration are all Administrator-only.

***

### Managing users

User management — viewing the current user list, inviting new users, changing roles, and removing users — is handled in **Settings → Users**. This section is only accessible to Administrators.

→ See the [Settings page](/cms/interface/settings-interface.md) for details

***

### Not to be confused with App User Roles

CMS User Roles control who can do what inside the CMS. **App User Roles** are a separate concept — they control which Locations end users of your app can see, search for, and navigate to. They are configured in Solution Details → App Settings → App Configuration, and are not related to CMS access.

→ [Learn about App User Roles](https://docs.mapsindoors.com/sdks-and-frameworks/web/other-guides/application-user-roles)


---

# 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/core-concepts/editor.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.
