> 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/filer-guide/settings.md).

# Settings

If you belong to an organization, the **Settings** link appears in the sidebar. It opens a dedicated settings area with its own sidebar navigation for managing your organization.

## Organization Profile

The main settings page lets you view and edit your organization's details:

* **Organization name**
* **Organization type**
* **Address**
* **Phone number**
* **Email**

Click **Save** after making changes.

{% hint style="info" %}
**📹 GIF:** Navigating to Settings in the sidebar, the settings area opening with its own sidebar navigation, editing the organization name and address on the Organization Profile page, and clicking Save.
{% endhint %}

## Team Members

The Team Members page shows everyone in your organization and lets admins manage the team.

* **Member list** -- Shows each member's name, email, role, and active status, sorted alphabetically by last name.
* **Pending invites** -- Shows invitations that have been sent but not yet accepted, including who sent them and when they expire.
* **Invite new members** -- Admins can send email invitations to add new team members to the organization.

{% hint style="info" %}
**📹 GIF:** The Team Members page showing the member list and pending invites, then clicking "Invite" to open the invite dialog, entering an email address, and sending the invitation.
{% endhint %}

## Billing

The Billing page is where admins manage the organization's shared payment method and handle failed payments.

### Organization Payment Card

Your firm can have a shared credit or debit card on file for filing fees. The card is displayed as a visual card showing the brand, last four digits, and expiration date.

* **Add a card** -- If no card is on file, click the placeholder to open the card entry form. Card details are stored securely by the payment processor -- the system never sees your full card number.
* **Update the card** -- Click the **Update** button below the card to replace it with a new one.

When individual filers submit filings, they can choose to use the organization card or their personal card during the Fees step.

### Failed Filings

If any filings in your organization have failed payments, they appear in a table below the card. You can see each filing's number, filer name, amount, and the date the payment failed.

Click **Retry All** to attempt payment again on all failed filings at once. After updating the card, you will also be prompted to retry failed payments automatically.

{% hint style="info" %}
**📹 GIF:** The Billing page showing the visual card display with brand and last four digits, the failed filings table below, clicking "Update" to change the card, then clicking "Retry All" to reattempt payments.
{% endhint %}

### Billing Contact

Admins can set a billing contact email address for payment-related notifications.

## Preferences

The Preferences page shows upcoming configuration options for your organization. These features are coming soon:

* **Default Court** -- Set a default parish for new filings across your organization.
* **Filing Defaults** -- Pre-fill case type, document type, and party information for common filing patterns.
* **Fee Waivers** -- Configure fee waiver request policies for your organization.


---

# 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:

```
GET https://docs.cottfile.com/filer-guide/settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.