> 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/edit/actions-toolbar/barrier-route-element.md).

# Barrier Route Element

A Barrier is a route element you place on the Route Network to modify how wayfinding works at a specific point — without a physical door being present.

Use barriers to close off hallways, add delays, restrict access by user role, or enforce one-way routing.

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

***

### When to use a Barrier

Barriers are useful when you need to influence routing but there is no door to place a Door Route Element on. Common use cases include:

* Blocking a hallway that should not be used for navigation
* Adding a delay to a route that passes through a slow area, like a security checkpoint
* Restricting access to a zone for certain App User Roles
* Enforcing one-way movement through a corridor or entrance

***

### Adding a Barrier

1. In the Actions Toolbar, click **Show Network** to make the route network visible
2. Click **Add Barrier Route Element**
3. Click on the map at the point where you want to place the barrier
4. The Barrier editor panel will open — configure the settings below
5. Click **Save**
6. Click **Reload Route Network** to apply your changes

> **Note:** Always reload the Route Network after saving changes to a barrier, otherwise the changes will not be reflected in your app.

***

### Barrier Settings

**Restrictions** Controls who can pass through this barrier.

* **Open for all** — All users can pass through. No restriction applied.
* **Open for specific App User Roles** — Only users with the selected roles can pass through. Select one or more App User Roles from the list.
* **Closed for all** — No users can pass through. The route will be blocked entirely.

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

**Delay (seconds)** Adds a time penalty to any route that passes through this barrier. Used in estimated travel time calculations. Useful for areas that slow people down — such as a busy intersection, a turnstile, or a steep ramp.

**Radius (meters)** Sets the radius of the barrier to ensure it correctly intersects the Route Network. Increase this value if the barrier doesn't appear to be connecting to the network paths.

**Floor Index** Sets which floor the barrier is placed on. By default this is set to the currently active floor. Change this if you need to move the barrier to a different floor.

> **Note:** The Floor Index can differ from the Floor name shown in the Floor selector. For example, the Floor named "1" may have the index `10`. Check that you are using the correct Floor Index before saving.

**One-way direction (bearing)** Enforces one-way movement through this point. 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.

**Element details** At the bottom of the editor, below the settings, you can see information about the barrier: its Id, Latitude and Longitude, Last modified by (the user who last changed it) and Last modified (when it was last changed).

***

### Editing or deleting a Barrier

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

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

***

> **Tip:** If you want to restrict access through a door rather than an open path, use a Door Route Element instead — it offers the same restriction options plus door-specific settings like type and snapping behaviour.


---

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