> For the complete documentation index, see [llms.txt](https://docs.saaster.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saaster.io/development/develop-with-saaster/general-services/mappings-and-rigths-management.md).
# Mappings and rigths management
As you have already seen in chapter System Mappings, we use a mapping for the readable URLs, which runs through the database. Here you can find out how it is structured.
The relevant function for the mappings is the *getSEF()* function, which is called in application.cfc. In it, we resolve the URL and redirect the user to the right page.
* strMapping is the url string in the browser
* strPath is the corresponding file which is loaded by saaster
* The three “admin” columns are for the right management
We currently only operate a small rights management system in saaster, which is reduced to the individual pages. Depending on the status of the logged-in user, the pages are blocked or can be accessed.
If all three boolean values are set to 0, a normal user can also call up the page
---
# 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://docs.saaster.io/development/develop-with-saaster/general-services/mappings-and-rigths-management.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.