> 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/organizations.md).

# Organizations

The **Organizations & Filers** page gives platform administrators a platform-wide view of registered filers, organizations, and sign-up activity -- and the tools to manage them.

## The Overview

At the top of the page, stat cards summarize the platform:

* **Organizations** -- total registered firms and agencies
* **Total Filers** -- all filer accounts
* **Solo (no org)** -- filers not attached to any organization
* **New (last 30d)** -- recent sign-ups, with a count for the last 7 days

Below the cards, three searchable tabs: **Recent Sign-ups**, **Organizations**, and **Solo Filers**.

## Creating an Organization

Click **New Organization** to create an organization that filers can be assigned to. Enter the **Name**, **Type** (Law Firm, Government Agency, etc.), **Contact email**, and **Phone**, then click **Create Organization**.

{% hint style="info" %}
Filers can also create their own organizations during onboarding or from Filer Portal → Settings. Admin-created organizations are useful when you want to set a firm up before its members sign up -- for example, ahead of a parish go-live.
{% endhint %}

## Managing an Organization

Each organization row has a **Fee exempt** toggle -- turn it on for government agencies or other organizations that should never be charged filing fees.

Expanding a row shows two sections:

### Members

The roster lists everyone who belongs to the organization -- including members currently **switched to another practice** (a filer can hold several firms on one account). Each member row shows Name, Email, Phone, Role, Bar #, Filings, and Status, with two actions. Both act on **this organization's row** for the member, never on whichever practice they happen to have active:

* **Edit** -- opens **Edit user access**:
  * **Email address** -- changes their sign-in address immediately (no verification email is sent).
  * **Primary role** -- changing to a court-staff role removes the user from any organization.
  * **Organization admin** -- a secondary capability layered on the primary role: they can manage the team, billing, and the org card while keeping their role. Per practice -- granting it here gives nothing in the member's other firms.
  * **Show accounting** -- shows the Reports tab with organization filings, fees, and revenue. Also per practice.
* **Move to org** -- moves **this membership** to a different organization; any other practices the filer holds are untouched. A **Make organization admin** toggle controls their standing in the new firm (granted on the destination's membership, never as a global role). The only admin of a firm with other members cannot be moved out until another admin is assigned. Filings already submitted under the old firm stay on its record.

### Pending Invites

Shows each outstanding invite's Email, Invited By, Sent, and Expires, with **Resend** (issues a fresh 7-day invite) and **Revoke** actions. Click **Invite Member** to send a new invite by email address.

## Solo Filers

The **Solo Filers** tab lists filers with no organization. Use **Move to org** to attach them to a firm -- handy when someone signed up without finding their firm.

## Org Self-Service

Organization members manage their own settings from **Filer Portal → Settings**, including the organization profile, team invites, join-request approvals, and the shared billing card. For details, see [Filer Settings](/filer-guide/settings.md).

{% hint style="info" %}
**📹 GIF:** Expanding an organization row -- viewing members, editing a member's access, and resending a pending invite.
{% endhint %}


---

# 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/organizations.md?ask=<question>&goal=<user_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.