> 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/matters/collaborating-across-matters-in-paxton.md).

# Collaborating Across Matters in Paxton

Share a matter with people in your organization so everyone works from the same files, chats, and drafts.

Share a matter with people in your organization and everyone works from the same files, drafts, records, and tables. Each person signs in with their own account, and access is managed per matter.

### Roles

| Role            | What they can do                                                                       |
| --------------- | -------------------------------------------------------------------------------------- |
| **Owner**       | Everything, including managing members. The person who creates a matter is its owner.  |
| **Editor**      | Manage matter details, files, and records. View any chat, and edit any draft or table. |
| **Contributor** | Manage files, and view any record, chat, draft, or table.                              |

{% hint style="info" %}
Editor access to billing summaries and drafts is coming soon.
{% endhint %}

### Share a matter

1. On the **Matters** page, click **⋮** on the matter and choose **Manage members**. Or open the matter and click **Add Members** at the top right.
2. At the top right of the dialog, choose a role: **Contributor** or **Editor**.
3. In **Search your organization**, find and select the people to add. You can add several at once.
4. Click **Add Members**. They appear under **Who has access**.
5. Click **Done**.

You can also add team members when you create a matter.

<figure><img src="https://1404317777-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCY0Bz9NWp8rqtfuqg7ne%2Fuploads%2FyJacrLyXGaxq49QqUyPH%2Fmanage-members-roles.png?alt=media&amp;token=bff3dac8-37f8-4eb4-9773-4ef6c47c3bf6" alt=""><figcaption></figcaption></figure>

### Accept an invitation

A matter shared with you appears on your **Matters** page with a **Pending** label. Open it and click **Accept** to start working in it, or **Reject** to decline.

### Work in a shared matter

* **See who has access**: member avatars appear at the top right of the matter. The **Access** column on the Matters page shows **Only you**, **Pending**, or the member count.
* **Review a teammate's work**: chats and drafts created by someone else open in view-only mode. To build on a teammate's chat, click **Start your own chat**.
* **One editor at a time**: only one person can edit a draft in Canvas at once.

### Change who has access

Owners can reopen **Manage members** at any time to add people or review roles.

### Related articles

* [Using Matters in Paxton](https://help.paxton.ai/help/matters/using-matters-in-paxton)
* [Organization Settings](https://help.paxton.ai/help/other-topics/organization-settings)
* [Security & Compliance](https://help.paxton.ai/help/other-topics/security-and-compliance)


---

# 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/matters/collaborating-across-matters-in-paxton.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.
