> For the complete documentation index, see [llms.txt](https://docs.fiveroster.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fiveroster.com/player-management/understanding-roster-access-levels.md).

# Understanding roster access levels

Your roster has specific access levels that determine what a player accessing the roster can do depending on their assigned roster rank. You can add/remove roles from ranks at any time and you can learn how to make those changes by [clicking here](/roster-creation/adding-ranks-and-sections.md).

### :red\_circle: Administrator

Administrators have access to amend the roster completely. They can clear ranks, assign players to specific ranks, promote/demote players and manage player strikes. Ranks with the access of Administrator are unrestricted.

### :yellow\_circle: Manager

Managers cannot change the roster itself but can clear ranks, assign players to specific ranks, promote/demote players and manage player strikes.

### :white\_circle: Read-Only

Players with read-only access can only view the roster. They cannot manage ranks or players on the roster.


---

# 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.fiveroster.com/player-management/understanding-roster-access-levels.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.