> For the complete documentation index, see [llms.txt](https://docs.rairprotocol.org/rairprotocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rairprotocol.org/rairprotocol/codebase/rairdapp/rairnode/permissions-and-access-controls.md).

# Permissions and Access Controls

<figure><img src="/files/H4HkaFBfHdgU5FoeXqsq" alt="" width="473"><figcaption></figcaption></figure>

## Overview

Who controls access to what is of paramount importance to the mission of the RAIR project.  Effectively all permissions in RAIR are governed by a valid sessionID that is generated either from valid onchain or offchain data by the RAIRnode.&#x20;

## On-chain vs Off-chain Checks

As currently configured:&#x20;

* Onchain checks (from blockchain data) are required for: Admin access. DRM unlocking of videos.&#x20;
* Offchain checks (from internal database) are required for: Superadmin access. Setting user flags like Yoti age verification.&#x20;

## SessionID

Browser cookies delineate access to RAIR. The process for validating all users is the same:&#x20;

1. Send a valid user's 0x address to the RAIRnode
2. Validate onchain or offchain the correct parameters
3. Pass a valid SessionID to the users browser.&#x20;

## User Types&#x20;

Successful RAIR Validation offers tooling for 3 types of user by default:

* **Type 1 - Basic user.** Low-level access. Users accessing deployed systems to buy/sell NFTs, consume content etc.
* **Type 2 - Admin/Creator.** Mid-level access. Users can deploy NFT collections, update their metadata, upload videos, etc.
* **Type 3 - Superadmin.** Top-level access. Full control over deployment of the system. Site wide UI/UX, showing and hiding collections, setting, site wide royalties etc.&#x20;


---

# 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.rairprotocol.org/rairprotocol/codebase/rairdapp/rairnode/permissions-and-access-controls.md?ask=<question>&goal=<endgoal>
```

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