> 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. Filing types, docket entries, and fee schedules are read-only mirrors of Verdict CMS. {% 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 court, with user count, pending queue items, and an e-filing status badge. 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 | | **Audit Log** | Read-only, filterable record of platform activity (coming soon) | ### 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: | Section | Purpose | | ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- | | **Overview** | Parish stats and recent filings | | **Users** | Manage court staff roles, divisions, stamp titles, and active status; invite new staff | | **Civil Queue** / **Criminal Queue** | Live review queue for each division (same table clerks use) | | **Filing Types** | Read-only mirror of case types and sub-types from Verdict CMS | | **Docket Entries** | Read-only mirror of document types from Verdict CMS | | **Fee Schedules** | Read-only mirror of fee schedules from Verdict CMS | | **Statements** | The court's portion of every charge, refund, and chargeback in a period | | **Announcements** | Create and manage court announcements | | **Config** | Court settings: name, code, state, jurisdiction label, external ID, e-filing toggle, Verdict civil/criminal codes (ValPay accounts shown read-only) | {% hint style="info" %} **Read-only Verdict data:** Filing Types, Docket Entries, and Fee Schedules are managed in Verdict CMS and auto-upsert at runtime. The Admin Panel only displays them — you cannot create, edit, or delete these records here. {% endhint %} {% hint style="info" %} **Queues and routing rules are configured in the Clerk settings area**, not the Admin Panel. See [Queues and Routing](/admin-guide/queues-and-routing.md). {% endhint %} ## Getting Started Parishes (courts) are provisioned directly in the database following a go-live checklist — there is no "create a court" 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, divisions, and stamp titles on the Users page 3. **Post announcements** to inform filers of any important notices 4. **Monitor the Civil and Criminal queues**, Statements, and Reports as filings come in Filing types, docket entries, and fee schedules require no setup here — they sync from Verdict CMS automatically. --- # 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/overview.md?ask=&goal= ``` `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.