> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/app/structural-user-access/users-tonic-managing.md).

# Managing organization users

{% hint style="info" %}
**Required global permission:** Manage access to Tonic Structural
{% endhint %}

The **Access Management** tab on **Structural Settings** view includes a list of the all of the users in your organization.

From the list, you can remove Structural users. You can also restore removed users. If you do not use SSO to manage users, then you can reset passwords for Structural users.

For information on how users are added to Structural, go to [Logging into Structural for the first time](/app/logging-into-structural-for-the-first-time.md).

You do not use the **Users** list to manage user permissions.

* To [assign global permission sets](/app/structural-user-access/permissions/global-permissions/global-permission-set-access.md), use the **Global Permission Sets** tab.
* To [assign team permission sets](/app/structural-user-access/permissions/team-permissions/configuring-access-to-team-permission-sets.md), use the **Team Permission Sets** tab on **Team Settings**.
* To [assign workspace permission sets](/app/workspace/workspace-access-management/workspace-sharing.md), go to **Workspaces** view.

## Viewing the Users list

To display the **Users** list:

1. In the Structural heading, click **Structural Settings**.
2. On **Structural Settings** view, click **Access Management**.
3. On the **Access Management** tab, click **Users**.

<figure><img src="https://3378426797-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LSQCLFQ4bslJ-HYc8c3%2Fuploads%2FL4GPPqd5Fx0nIAqlvcTF%2FTonicUsers.png?alt=media&amp;token=433f1fb9-682b-4647-bae2-bfb44a77bbd9" alt=""><figcaption><p>Users list on the Access Management tab of Structural Settings</p></figcaption></figure>

For each user, the list includes the following information:

* Name
* Email address
* When the user was most recently active in Structural

To use a column to sort the list, click the column heading. To reverse the sort order, click the column heading again.

## Removing an organization user

You can remove an organization user from the **Users** list.

To remove an organization user:

1. In the **Users** list, click the actions menu, then click **Remove User**.
2. If the user is the owner of any workspaces, then Structural warns you that the workspaces will no longer have an owner.\
   \
   The workspaces are moved to the **Workspaces Without An Owner** list on **Team Settings**. For more information, go to [Managing workspaces that do not have an owner](/app/workspace/managing-workspaces/workspaces-no-owner.md)
3. On the **Remove User** panel, click **Remove**.

Note that when you remove a user, it does not remove the user from the value of the `TONIC_ADMINISTRATORS` environment setting. You must [update the environment setting manually](/app/structural-user-access/permissions/global-permissions/managing-admin-users.md). If a user or group is later added that has an email address or group name that is in the environment variable value, that user or group is granted the built-in Admin (Environment) permission set.

## Restoring a removed user <a href="#users-restore-deleted" id="users-restore-deleted"></a>

You can restore a removed organization user. When you restore a user, Structural restores to the user the global permission sets that they were assigned.

To view the list of removed, users, on the **Access Management** tab of **Structural Settings**, click **Deleted Users**.

<figure><img src="https://3378426797-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LSQCLFQ4bslJ-HYc8c3%2Fuploads%2FpohRkuZhju1MhXcAuXsR%2FAccessManagementDeletedUsers.png?alt=media&amp;token=c1d060d2-02d7-44d7-9b18-1bb462610bbc" alt=""><figcaption><p>Deleted Users list</p></figcaption></figure>

To restore a removed user:

1. In the **Deleted Users** list, click the restore icon for the user.
2. On the confirmation panel, click **Restore User**.

## Resetting a user password

{% hint style="info" %}
**Required global permission:** Reset Tonic user passwords
{% endhint %}

From the **Users** list, if your instance does not use SSO to manage users, you can reset a user's password. You would most likely do this in response to a request from a user who forgot their password.

The reset password option sends an email to the user to allow them to set up a new password.

To reset a password, in the **Users** list, click the actions menu for the user, then click **Reset Password**.


---

# 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.tonic.ai/app/structural-user-access/users-tonic-managing.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.
