# 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.

<figure><img src="https://4165049393-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuUY7tl3j0xMLQbwSQOYv%2Fuploads%2FNV2oN2EzP55XtpsVjeGw%2Fimage.png?alt=media&#x26;token=2ea15919-171e-4802-9031-08127b221af1" alt=""><figcaption></figcaption></figure>

* 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
