# Door Route Element

<figure><img src="/files/QPuHiVdo8VsDwkMg4np9" alt=""><figcaption></figcaption></figure>

> **Note:** Door Route Elements can only be added on solutions with Automatic Graph Setup. If you have a Manual Graph Setup, contact [MapsPeople Support](https://mapspeople.atlassian.net/servicedesk/customer/portals) to request door changes.

***

### Adding a Door

1. In the Actions Toolbar, click **Show Network** to make the route network visible
2. Click **Add Door Route Element**
3. Click on the map where the door is located — by default, doors snap to the nearest wall geometry
4. The Door editor panel will open — configure the settings below
5. Click **Save**
6. Click **Reload Route Network** to apply your changes

> **Tip:** Hold **Shift** while placing a door to snap it to the midpoint of the nearest wall, or to the corner of the nearest polygon. This makes precise placement much easier.

***

### Door Types

Every door must have a Type. The type determines the door's default behaviour and how it connects spaces.

| Type                  | Description                                                         |
| --------------------- | ------------------------------------------------------------------- |
| **Door**              | A standard door between two rooms inside the same building          |
| **ElevatorDoor**      | A door for an elevator — comes with a built-in delay                |
| **ExternalDoor**      | Links to the outdoor route network — only connects to one room      |
| **InterBuildingDoor** | Connects two rooms in two different buildings                       |
| **Opening**           | An open entryway between two rooms with no physical door            |
| **Hatchway**          | A specialised door type for smaller or specific room configurations |

***

### Door Settings

**Restrictions** Controls which users can pass through this door.

* **Open for all** — All App User Roles can use this door
* **Open for specific App User Roles** — Only selected roles can pass through. If no roles are selected, the door automatically becomes Closed for all
* **Closed for all** — No users can pass through this door

**Delay (seconds)** Adds a time penalty to routes passing through this door. Used in estimated travel time calculations. ElevatorDoors include a default delay — adjust this to match your real-world elevator wait times.

**Radius (meters)** Sets the radius of the door to ensure it correctly intersects the Route Network. Increase this if the door isn't connecting to the network paths.

**Floor Index** Sets which floor the door is placed on. Defaults to the currently active floor.

**One-way direction (bearing)** Enforces one-way movement through this door. Enter a bearing in degrees (0–360) representing the direction users are allowed to exit. For example, a value of 45 means users can only exit heading north-east.

***

### Creating multiple doors at once

For solutions where you need to place many doors quickly, two keyboard shortcuts unlock bulk creation modes:

**Multiple doors with fixed width** `Ctrl + Shift + D` (Windows) / `Shift + Control + D` (Mac) Places multiple doors of the same fixed width in sequence.

**Multiple doors with custom width** `Ctrl + Shift + F` (Windows) / `Shift + Control + F` (Mac) Places multiple doors where you can define the width of each individually.

In both bulk modes, you can select the door Type for all doors being created and undo the last placement. All other settings must be configured individually for each door after creation.

***

### Editing or deleting a Door

To edit an existing door, make sure the Route Network is visible, then click the door on the map to open its settings panel. Make your changes, click **Save**, then **Reload Route Network**.

To delete a door, open it and click **Delete**, then reload the Route Network.

***

> **Tip:** If you need to restrict routing at a point where there is no physical door, use a Barrier Route Element instead.


---

# 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/actions-toolbar/door-route-element.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.