> 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 permissions in skadii depend on your assigned user role.

### What user roles are available?

* **user**
* **admin**

Your user role determines which HTI apps and skadii tools you can view and use.

### What permissions do users have?

Users receive their permissions from an admin and only see the apps, tools, and features they are authorized to access.

### What administrator roles are available?

skadii provides two different administrator roles:

**Workspace Admin**

The Workspace Admin manages the entire organization and can:

* invite and manage users
* manage access to HTI apps and skadii tools
* maintain an overview of the entire workspace

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

The Site/Plant Admin manages one or more sites or assets, such as ropeways, fleet vehicles, or snowmaking systems.

For the assigned sites and assets, the Site/Plant Admin can:

* assign and manage user permissions
* invite or 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.skadii.com/documentation/docs-en/get-started-now/user-roles.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
