> 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, dockets, 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 (with "(you)" after your own), parish code, email, role, docket, an **Active** toggle, and Edit/Remove actions. You can search by email and filter by: * **Role** -- All, Clerk, Judge, Judicial Staff, or Court Admin * **Docket** -- All, 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** | Chambers staff supporting one or more judges | | **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** -- there is no form for creating an account with a password. Click **Invite Staff Member** and fill in: * **Email** (e.g., "") * **Role** -- Clerk, Judicial Staff, Judge, or Court Admin * **Docket** -- Both, Civil, or Criminal The dialog notes: "An invitation email will be sent. The link expires in 7 days." The invitee follows the link to set up their own account. {% hint style="info" %} When inviting **Judicial Staff**, the dialog reminds you: after they accept the invite, edit their account here to link them to their judge(s) -- until then their inbox will be empty. {% endhint %} If an invite cannot be sent, you'll see why: "A pending invite already exists for this email" or "This person is already a member of your court". ### Pending Invitations Invites that have not yet been accepted are listed in a **Pending Invitations** table showing Email, Role, Docket, Sent, and Expires. You can **revoke** a pending invite; to send a fresh link, revoke the old invite and create a new one. ## Editing a Staff Member Click the **pencil icon** on a row to open the edit dialog. The fields shown depend on the person's role: * **Role** -- Clerk, Judge, Judicial Staff, or Court Admin. You cannot change your own role * **Docket** -- Civil, Criminal, or Both. Shown for **every** staff role, judges included * **Stamp title** (Clerk and Court Admin) -- the title shown after this clerk's name on the e-file stamp (e.g., "Deputy Clerk", "Chief Deputy Clerk"). A live preview shows exactly how the stamp line will read: "by First Last, Title". Leave blank to show no title * **Judges served** (Judicial Staff) -- checkboxes linking the staff member to judges. As the dialog explains: "Judicial staff see the inbox of every judge they're linked to. They can review, mark up documents, and leave notes — but cannot sign or deny." * **Additional parishes** (Judge and Judicial Staff; **platform admin only**) -- grants access to other parishes in the same judicial district. The home parish is always included. The dialog warns that every parish is listed, so check that the one you pick really is in this judge's district before granting it Click **Update** to save, or **Cancel** to close without changes. {% 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. * Deactivating a staff member **releases any filings held by them after signing**, so signed work does not get stuck in a departed employee's queue. * Deactivated staff receive **no notification emails**. ## Removing a Staff Member Click the **trash icon** on a row to remove a staff member from the court. You are asked to confirm ("Remove {name} ({email}) from this court?"). 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.cottfile.com/admin-guide/managing-users.md?ask=&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.