> For the complete documentation index, see [llms.txt](https://help.paxton.ai/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paxton.ai/help/other-topics/organization-settings.md).

# Organization Settings

Create an organization, invite your team, and manage member roles.

An organization lets your team use Paxton together under one subscription. Admins invite members, manage roles, and handle billing.

### Open your organization settings

1. Click your name at the bottom of the left sidebar to open the account menu.
2. Click **Settings**.
3. Under your organization's name, click **Members** or **Billing**.

The account menu also shows your organization name, member count, and an **Invite members** shortcut.

\[\[SHO![](https://1404317777-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCY0Bz9NWp8rqtfuqg7ne%2Fuploads%2FGqh92xMwz53yPdd88rK5%2Fsettings-members.png?alt=media\&token=6a539d0d-7f97-415b-ba3f-6c0a3cfe8ba7)T:settings-members]]

### Create an organization

1. Open the account menu and click **Settings**.
2. Go to **Billing** and choose the option to create an organization.

### Invite members

1. In **Settings > Members**, click **Invite Members**.
2. Enter each person's work email and send the invitations.

Invited people get an email with instructions. Until they accept, they appear with a **Pending** label and count toward **Pending invites** on the Billing page.

{% hint style="info" %}
Use the email address each person will sign in with. An invitation can't be accepted from a different address.
{% endhint %}

### Member roles

| Role      | What they can do                                                            |
| --------- | --------------------------------------------------------------------------- |
| **Admin** | Invite and remove members, change roles, and manage the subscription.       |
| **User**  | Use Paxton on a seat in your organization. Can't manage members or billing. |

To change a role, click the **⋮** menu on the member's row and choose **Change role to user** or **Change role to admin**.

These organization roles are separate from matter roles (owner, editor, contributor). See [Collaborating Across Matters in Paxton](https://help.paxton.ai/help/matters/collaborating-across-matters-in-paxton).

### Remove a member or cancel an invitation

1. In **Settings > Members**, find the person.
2. Click the **⋮** menu on their row and choose **Remove from organization**.

Removing someone ends their access to your organization. Use the same menu on a pending row to cancel an invitation.

To leave an organization yourself, click **Leave Organization** at the bottom of the Members page.

### Related articles

* [Billing and Account Settings](https://help.paxton.ai/help/other-topics/billing-and-account-settings)
* [Collaborating Across Matters in Paxton](https://help.paxton.ai/help/matters/collaborating-across-matters-in-paxton)


---

# 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://help.paxton.ai/help/other-topics/organization-settings.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.
