> For the complete documentation index, see [llms.txt](https://docs.steadybit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.steadybit.com/install-and-configure/manage-teams-and-users/users.md).

# Users

This page describes user roles, how to invite users, and how external identity systems affect user management.

## Role Types

Users have two role types that determine access and permissions:

* Platform role: Assigned at the platform (tenant) level. Each user has exactly one of `admin` or `user`.
* Team role: Assigned within a specific team. A user can be an `owner` or a `member` in that team.

See [Permissions](/install-and-configure/manage-teams-and-users/permissions.md) for the functional differences between these roles.

{% hint style="info" %}
Users who are not members of any team do not count toward license limits.
{% endhint %}

## Inviting Users (SaaS only)

New users can be invited by email and directly assigned to teams and roles. When an invitation is accepted, the corresponding user is created and gains access to your Steadybit tenant.

## Integrations

User management can be automated by the [OIDC Integration](/install-and-configure/install-on-prem-platform/oidc-integration.md) and [LDAP Integration](/install-and-configure/install-on-prem-platform/ldap-integration.md).


---

# 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.steadybit.com/install-and-configure/manage-teams-and-users/users.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.