# Source: https://docs.coollabs.io/coolify/v3/iam.md

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coollabs.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Identity & Access Management

## Users

After you successfully installed Coolify, you can start configuring it via the provided UI.

### Registration

The first registered user will be the `root/admin` user (with id 0) of your Coolify instance. This user will see and change all resources deployed, access system-wide configurations, initiate the one-click update process, etc.

<Tip>
  After the first user is registered successfully, `registration is disabled` to prevent unwanted registrations.

  You can enable registration in the `Settings` menu.
</Tip>

Every other user won't access system-wide configurations and only see their own team's resources.

### Authentication Methods

`Email/password` registration is supported.

### Reset Password

Admins can reset the passwords of team members in the `Settings` menu. If a password reset is requested, the user has 10 minutes to do it.

Password reset is done through the login process. The user's new password will be the one used on the login form.

After 10 minutes, the old password can be used to log in, and the password reset process is stopped.

## Teams

Each registered user has its own team automatically. Each team only has access to its own resources.

You can register any number of teams and invite any number of users to it.

You can only access other team's resources if someone with an `admin` privilege invites you to that team.

### Privileges

Team members could have two kinds of privileges:

* `admin` has the same privileges as the `owner` of the team.

Admin can check, modify, delete any resources that are owned by the team.

* `read` can only read things.

### Root Team

With the first user, a `root team` is also created with id `0`.

Users in this team have the same privileges as the first user so that they see and change all resources deployed, access system-wide configurations, initiate one-click update process, etc.