> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/user-access.md).

# User Access

#### ***Applies to version(s): v2.5, v2.6.***

The Web Portal is designed to provide varying degrees of write and read privileges to users. Each configuration, when created, is given a privilege level (integer value from 0 to 9).

By default, the root user is given full read and write access. This is required so that the root user can function as the system administrator without any restrictions imposed. Subsequent users can be created with the ability to read and write, or just to read. An integer value from 0 to 9 is assigned to each user.

### Read/Write user access levels in the Web Portal

![User access levels](https://docs.telcobridges.com/w/images/0/01/User-access-levels.jpg)

**For example:**

* A user with an access level of 0 has access to configurations created with levels 0 to 9.
* A user with an access level of 4, will have access to configurations created with privilege levels 4 to 9.
* Configurations created with privilege levels 0 to 3 will be invisible to user levels 4 to 9.


---

# 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://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/user-access.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.