> For the complete documentation index, see [llms.txt](https://docs.cottfile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cottfile.com/admin-guide/managing-users.md).

# Managing Users

The Users page (titled **Court Staff**) manages the court staff for a single parish. Open a parish from the **Parishes** card grid, then choose **Users** in the parish sidebar. From here you manage staff roles, divisions, stamp titles, and active status, and you invite new staff by email.

{% hint style="info" %}
This page manages **court staff only** — Clerk, Judge, Judicial Staff, and Court Admin. It does not manage filer accounts (attorneys, pro se litigants, organization admins, government filers). Filer accounts are created through registration and onboarding.
{% endhint %}

## Viewing Staff

The staff table lists everyone assigned to this court. Each row shows the staff member's name, parish code, email, role, division, and an active toggle. You can search by email and filter by:

* **Role** -- Clerk, Judge, Judicial Staff, or Court Admin
* **Division** -- Civil, Criminal, or Both
* **Status** -- Active, Inactive, or All

## Court Staff Roles

| Role               | Description                                                                                                          |
| ------------------ | -------------------------------------------------------------------------------------------------------------------- |
| **Clerk**          | Reviews and processes filings in the review queue                                                                    |
| **Judge**          | Judicial officer. Reviews filings routed for judicial signing                                                        |
| **Judicial Staff** | Staff supporting a judge                                                                                             |
| **Court Admin**    | Full administrative access for the court. Can configure queues, routing rules, users, and other clerk-settings pages |

## Inviting Staff

New court staff are added by **email invite**, not by creating an account with a password. In the **Court Staff** section below the table, send an invite to the staff member's email address. They receive a link to set up their own account. Pending invites are listed until they are accepted or expire.

## Editing a Staff Member

Click the **pencil icon** on a row to open the edit dialog. You can change:

* **Role** -- Clerk, Judge, Judicial Staff, or Court Admin
* **Division** -- Civil, Criminal, or Both (shown for Clerk, Judicial Staff, and Court Admin roles)
* **Stamp title** -- The title shown after this clerk's name on the compact e-file stamp (e.g., "Deputy Clerk", "Chief Deputy Clerk"). Leave blank to show no title

Click **Update** to save.

{% hint style="warning" %}
You cannot change your own role. This prevents accidentally locking yourself out.
{% endhint %}

## Activating and Deactivating Staff

Use the **Active** toggle on each row to activate or deactivate an account. Deactivated users lose access. You cannot deactivate your own account.

## Removing a Staff Member

Click the **trash icon** on a row to remove a staff member from the court. You are asked to confirm first. You cannot remove your own account.


---

# 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.cottfile.com/admin-guide/managing-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.