> For the complete documentation index, see [llms.txt](https://docs.charted.com/ap-automation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.charted.com/ap-automation/charted-configuration/payment-automation/user-permissions.md).

# User permissions

This page covers who can do what in Payment Automation and how to assign it. Open **Charted > AP Automation > Settings > Permissions**.

<figure><img src="https://4244775538-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDi74GwuQpTYzdGbZQFpz%2Fuploads%2F9iwxDVP8J002dP2PdOLD%2Fpa-permissions-list.png?alt=media" alt="The Permissions page"><figcaption></figcaption></figure>

## How Payment Automation permissions work

* Payment Automation permissions are separate from NetSuite roles. Changing a NetSuite role does not give or remove them.
* Users still need NetSuite login access and a NetSuite role that can view vendor bills and bill payments.
* Users with the NetSuite Administrator role have every Payment Automation permission. No other role or employee has any by default.
* The Permissions page shows one list of permission groups for every Charted product you have installed, so the Payment Automation groups appear alongside those for other products.

## The permission groups

| Permission                    | What it allows                                                                                                                                       |
| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Manage Business Entities**  | Create, edit and delete business entities and funding sources; complete business entity onboarding; verify funding sources; view transaction history |
| **View Business Entities**    | Read-only access to business entities, funding sources and transaction history                                                                       |
| **Manage Payees**             | View, create, invite and edit payees; add payee payment methods; view invitation history and payee payments. Cannot create or release payments.      |
| **View Payees**               | View payees, payee payments and invitation history. Cannot send invitations.                                                                         |
| **Approve Payment Methods**   | View payees, invitations and payment methods; approve or reject payment methods                                                                      |
| **Release Payee Payments**    | View, release and cancel payments; view transaction history, payees and payment methods                                                              |
| **Create Balance Transfers**  | View, create and cancel balance transfers. Cannot release them.                                                                                      |
| **Release Balance Transfers** | View, release and cancel balance transfers. Cannot create them.                                                                                      |

A balance transfer returns funds from a failed or cancelled payment to your bank account. Payment Automation does not do this automatically, so assign both balance transfer permissions before go-live. See [Handling failed and cancelled payments](https://docs.charted.com/ap-automation/charted-features/payment-automation/handling-failed-and-cancelled-payments.md#getting-funds-back-with-a-balance-transfer).

## Assigning a permission

1. Select the permission.
2. Press **Add**. In **Add Roles and Employees**, set **Type** to **Role**, **Employee** or **All Types**.
3. Select the roles or employees and press **Add**.
4. Check the **Assigned Members** list and press **Save**.

We recommend assigning by role where you can, because the permission follows people when their role changes. Employee assignments are more precise but need maintenance.

{% hint style="info" %}
Keep managing payees, approving payment methods and releasing payments with different people. Giving one person both **Create Balance Transfers** and **Release Balance Transfers** removes that separation. Limit **Approve Payment Methods** to the smallest group you can, and avoid giving administrator access to people who only need one permission.
{% endhint %}

## Next

[Importing payees](https://docs.charted.com/ap-automation/charted-configuration/payment-automation/importing-payees.md)


---

# 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.charted.com/ap-automation/charted-configuration/payment-automation/user-permissions.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.
