> For the complete documentation index, see [llms.txt](https://docs.skadii.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skadii.com/documentation/docs-en/get-started-now/user-roles.md).

# User roles

Your access rights in skadii depend on your user role.

### What user roles are there?

* **User**
* **Admin**

Your user role determines which HTI applications or skadii tools you can see and use.&#x20;

### What permissions do users have?

A user receives their permissions from their admin and only sees what has been enabled for them.

### What different administrator roles are there?

skadii has two different administrator roles.

**Workspace Admin**

The Workspace Admin is the administrator for the entire company and can:

* invite and manage users&#x20;
* manage access to HTI applications and skadii tools
* manage the entire workspace

**Site/Plant Admin**&#x20;

The Site/Plant Admin manages one or more systems or assets, such as ropeways, fleet vehicles, or snowmaking systems, and can:

* grant and manage user permissions
* invite and remove users


---

# 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.skadii.com/documentation/docs-en/get-started-now/user-roles.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.
