> For the complete documentation index, see [llms.txt](https://rpfs.gitbook.io/rpfs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rpfs.gitbook.io/rpfs/enforcing-gateways.md).
# Enforcing Gateways
By default RPFS needs atleast one Gateway to operate. You can use this gateway for all your files.\
By default also all your Folders and Files can be accessed via any custom Gateway you create. \
\
But if you want to restrict access to specific folders only via one gateway, you can do so by editing the Folder settings. This is handy if you want to restrict, split and monitor access to your files that belong to different NFT Collections, or Different Applications. \
\
To do so go to Files and Folders page, click on the Edit button for the specific Folder that you want to restrict, and in the side drawer uncheck "Use with any gateway" and select the specific gateway that you've already created previously.\
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://rpfs.gitbook.io/rpfs/enforcing-gateways.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.