> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/workspace/understand-user-roles.md).

# What's the difference between admins and employees?

Understand the difference between Admins, who work on requests in the admin console and must be invited, and Employees, who submit requests via Slack, Teams or the portal

Siit distinguishes between two main types of users - **Admin and Employee.**

**Admin** is usually a member of one of the business teams, who is receiving and working on requests from employees. They have an account with Admin console and therefore can log in to the Admin interface.

**Employee** is someone who submits requests, but is not receiving and reply to other employee’ requests. This would be most of your employees from your company.

**⚠️ Only Admin** need to be explicitly invited into the Admin console! By default, **Employee** only have access to Slack, Teams App (or the Employee portal) that is created automatically once when we import their information.


---

# 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.siit.io/guides/workspace/understand-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.