> 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/overview.md). # Overview The Admin Panel is a platform-administrator tool with a parish-first design: you pick a parish from a card grid, then see and manage everything about that parish. From here you manage parishes, organizations, users, reports, and per-parish settings. {% hint style="info" %} You must have the **Platform Admin** role to access the Admin Panel. If you don't see the Admin link in your sidebar, contact your system administrator. {% endhint %} ## Navigation The Admin Panel has two navigation contexts. ### Global sidebar ("Platform Admin") When you first open the Admin Panel, a left sidebar titled "Platform Admin" lists: | Section | Purpose | | ----------------- | --------------------------------------------------------------------------------------------- | | **Parishes** | Card-grid landing page listing every parish. Click a parish to manage it | | **Organizations** | View law firms and organizations registered on the platform (read-only) | | **Reports** | Cross-parish analytics: filing volume, rejection reasons, queue depth, and clerk productivity | | **Accounting** | Platform accounting. Visible only to designated super users | | **Audit Log** | Record of platform activity (coming soon). Visible only to designated super users | | **AI Assistant** | Coming soon | {% hint style="info" %} **Accounting** and **Audit Log** appear only for designated super users -- ordinary platform admins do not see these two sections. {% endhint %} ### Parish landing page The **Parishes** page shows a card for each parish. Each card shows the parish name, an **Active/Inactive** badge (whether e-filing is on), the user count, and how many civil and criminal filings are pending in its queues. ### Parish sidebar Clicking a parish opens that parish's own sidebar (titled with the parish name, with a "Back to Parishes" link). It is grouped into three sections: | Group | Pages | | -------------- | ------------------------------------------------------------ | | Operations | **Overview**, **Users**, **Civil Queue**, **Criminal Queue** | | Reference data | **Filing Types**, **Docket Entries**, **Fee Schedules** | | Administration | **Statements**, **Announcements**, **Config** | | Page | Purpose | | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Overview** | Parish stats -- Active Users, Pending in Queue, E-Filing Active/Inactive -- and a Recent Filings table (Case #, Filer, Status, Submitted) | | **Users** | Manage court staff roles, dockets, stamp titles, and active status; invite new staff. See [Managing Users](/admin-guide/managing-users.md) | | **Civil Queue** / **Criminal Queue** | Live review queue for each docket, with the full clerk actions | | **Filing Types** / **Docket Entries** | Read-only mirrors of Verdict CMS for most parishes; editable at standalone parishes. See [Case Types and Documents](/admin-guide/case-types-and-documents.md) | | **Fee Schedules** | Read-only fee schedule view | | **Statements** | The parish's portion of every charge, refund, and chargeback in a period. See [Payment Statements](/admin-guide/payment-statements.md) | | **Announcements** | Create and manage court announcements | | **Config** | Court settings: name, code, state, jurisdiction label, e-filing toggle, Verdict codes, standalone switch, stamp behavior (ValPay accounts shown read-only). See [Setting Up a Parish](/admin-guide/setting-up-a-court.md) | {% hint style="info" %} **Queue and routing-rule configuration lives in the Clerk settings area**, not the Admin Panel. See [Queues and Routing](/admin-guide/queues-and-routing.md). {% endhint %} ## What Only Platform Admins Can Do A few actions exist nowhere else in the system: * Turn the **Standalone** switch on or off for a parish (Config page) * Grant **Additional parishes** to judges and judicial staff whose district spans several parishes (Users page) * Choose **which parish a staff invitation goes to** * Work **any parish's queue and review filings** from the admin Civil/Criminal Queue pages (filings opened this way are not auto-claimed) ## Getting Started Parishes (courts) are provisioned directly in the database following a go-live checklist — there is no "create a parish" form in the Admin Panel. Once a parish exists, your day-to-day work in the panel is: 1. **Review the parish Config** — confirm the court name, codes, jurisdiction label, and Verdict civil/criminal codes are correct, and that e-filing is enabled 2. **Invite court staff** and assign their roles, dockets, and stamp titles on the Users page 3. **Monitor the Civil and Criminal queues**, Statements, and Reports as filings come in For parishes connected to Verdict, filing types, docket entries, and fee schedules require no setup here — they sync from Verdict CMS automatically. Standalone parishes manage their filing types and docket entries on these pages instead. --- # 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/overview.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.