---
title: "How to Manage Users"
description: "Add, edit, and manage user accounts and access on the Corridor platform."
---

<div style="padding: 14px 16px; border: 0.5px solid #AFA9EC; border-radius: 12px; background: #EEEDFE; margin-bottom: 1.5rem;">
  <div style="display: flex; align-items: center; gap: 7px; margin-bottom: 8px;">
    <svg width="16" height="16" viewBox="0 0 16 16" fill="none">
      <path d="M9 2L4 9h4l-1 5 5-7H8l1-5z" stroke="#7f77dd" stroke-width="1.2" stroke-linecap="round" stroke-linejoin="round"/>
    </svg>
    <span style="font-size: 11px; font-weight: 500; letter-spacing: 0.05em; text-transform: uppercase; color: #534AB7;">TL;DR</span>
  </div>
  <div style="font-size: 13px; color: #3C3489; line-height: 1.65;">
    In <strong>Settings → Users</strong>, create a user with an email and at least one role. Roles are the only thing that grant access, so a user with no role can sign in but sees nothing. You don't delete users; deactivate them with <strong>Is Active</strong>.
  </div>
</div>

:::note[Admin guide]
This page is for administrators. When the platform authenticates through an external provider (SAML or OAuth2), identity fields are managed by the provider and shown read-only, and the **User Roles** field is locked when authorization is external.
:::

## Concept

A **user** is a platform login. Identity fields (name, email, department) describe the person; the **roles** field is what grants access. A user with no role sees nothing.

## Before you start

* You need write access to Users in Settings.
* The [roles](/user-guide/admin-guide/configure-roles/) you'll assign must already exist.
* Under SSO, users are typically provisioned on first login with a default role (set in [Platform Settings](/user-guide/admin-guide/configure-platform-settings/)), so manual creation may not be needed.

## Create a user

<details open class="step">
<summary>

#### Open the Create Form

</summary>

Go to **Settings → Users**. </br>The page shows all existing users with their **Username**, name, **Email**, assigned **Role** (shown as `Workspace: Role`), **Last Login**, and whether they're **Active**.

Click **+ New User** at the top right.

</details>

<details open class="step">
<summary>

#### Fill in the Form & Save

</summary>

* **Username** <span style="color: #E5484D;">*</span> - the login name. Can be set only on creation; locked on edit.
* **First / Last Name**, **Department** - optional identity details.
* **Email** <span style="color: #E5484D;">*</span> - a valid address, used for notifications and approval requests.
* **Is Active** - on by default; turn off to block sign-in (see [Deactivate](#deactivate-a-user)).
* **User Roles** <span style="color: #E5484D;">*</span> - multi-select, each shown as `Workspace: Role`. This is what grants access. Locked when authorization is external.

Click **Save**. The user is created and can sign in with the roles you assigned.

</details>

## Reset a password

Reset is available under internal authentication only.

1. On the user's page, click **Reset Password**.
2. Enter a new **Password** and matching **Confirm Password**.
3. Click **Save**.

Passwords must be 8 to 60 characters and include an uppercase letter, a lowercase letter, a digit, and a special character from `!@#$%^&*_-`.

## Deactivate a user

There is no delete action. To block access, open the user, turn off **Is Active**, and save. </br>The user can no longer sign in, but their history and authored objects are preserved for audit. Turn **Is Active** back on to restore access.

## Check recent activity

Open a user and go to the **Activity** tab to see login stats:

* **Last Login Date**
* **Logins in Last 7 Days**
* **Logins in Last 30 Days**
* **Logins in Last Year**

Use it to spot dormant accounts before deactivating.

## What's next

* [Configure Roles and Permissions](/user-guide/admin-guide/configure-roles/): define what the roles you assign here can actually do.
* [Configure Platform Settings](/user-guide/admin-guide/configure-platform-settings/): set login methods and the default role for SSO users.