> For the complete documentation index, see [llms.txt](https://docs.adminremix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adminremix.com/asset-management/bundles/restriction-location.md).
# Restriction Location
Restrict users to viewing bundles based on location.
1. Whether you are an admin creating a bundle, or a restricted user, creating a location restricted bundle is simple. Start by clicking the + button and selecting Create. *\*Users will need create permissions.*
2. Next you will be prompted to name your bundle. This is where you will also have the option to select a location for the bundle and restrict access to that location. *\*If you are a restricted user, you will only be able to select your location.*
3. After clicking next, you will be prompted to select assets or items for the bundle. Save when you are finished. *\*This can be left blank for now if you are creating blank bundles.*
4. Your bundle will appear in the bundles list. *\*Restricted users will only be able to view bundles at their location.*
---
# 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.adminremix.com/asset-management/bundles/restriction-location.md?ask=&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.
