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

# User Management

## Overview

Organization admins can manage users, invitations, roles, and publication access from the settings experience and from publication details.

### User and invitation management

The **Users** page lists current organization members and their roles.

The **Invitations** page lists pending invitations. It gives admins a separate place to review who still needs to join the organization.

Invitation forms also let admins choose a role before the user joins.

#### Invite a user

1. Open **Settings**.
2. Open **Invitations**.
3. Select **Invite User**.
4. Enter the user's email address.
5. Select a role.
6. Confirm the invitation.

#### Find a user or invitation

1. Open **Settings**.
2. Open **Users** or **Invitations**.
3. Enter a name or email in the search field.
4. Apply role filters when needed.

### Role management

Roles control which actions are available in the interface. Admin-level access allows access to organization management tasks such as managing users, invitations, and publication access.

#### Change a user role

1. Open **Settings**.
2. Open **Users**.
3. Select the user to manage.
4. Choose **Edit** for the user's role.
5. Select the new role.
6. Save the change.

### Publication access management

Admins can manage publication access from publication details and from user management views.

#### Grant or revoke publication access

1. Open **Publications** and select a publication, or open the relevant access controls from **Settings**.
2. Review the current people with access list.
3. Search for the user when needed.
4. Select the new access level or choose the revoke action.
5. Confirm the change if the interface asks for confirmation.

### Admin restrictions and access behavior

Organization admins can open settings pages and complete management actions that lower access roles cannot use. Users without admin access may still see information that applies to them, but they cannot open admin-only management views or complete admin-only actions.

Publication and work areas also limit write actions based on the access level a person has for that publication. In those cases, a person may still view information without being able to complete write actions.<br>