> For the complete documentation index, see [llms.txt](https://docs.os.uk/os-downloads/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.os.uk/os-downloads/products/land-and-terrain-portfolio/os-mastermap-sites-layer/os-mastermap-sites-layer-technical-specification/enumerations/accessuserestrictionvalue.md).

# AccessUseRestrictionValue

### AccessPoint feature

Defines the values of the nature of any access restriction.

| Value             | Description                                                      |
| ----------------- | ---------------------------------------------------------------- |
| Disabled          | Access is restricted except for disabled access.                 |
| Emergency Access  | Access is restricted except for emergencies at this point.       |
| Guests            | Access is restricted except for guests at this point.            |
| Official Business | Access is restricted except for official business at this point. |
| Patrons           | Access is restricted except for patrons at this point.           |
| Residents         | Access is restricted except for residents at this point.         |
| Through Traffic   | Access to through traffic is permitted at this point.            |


---

# 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.os.uk/os-downloads/products/land-and-terrain-portfolio/os-mastermap-sites-layer/os-mastermap-sites-layer-technical-specification/enumerations/accessuserestrictionvalue.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.