> 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/approval-automation/role-permissions-and-approval-controls.md).

# Role Permissions and Approval Controls

### **Abstract** <a href="#id-9u08q3m5gtkd" id="id-9u08q3m5gtkd"></a>

Administrators managing vendor bill approvals in *NetSuite* must configure role-based permissions to ensure that only authorized users can take specific actions in the approval process. By setting up the *Permissions* tab in *Approval Workflow Automation (AWA)*, you define which employee roles can cancel approvals, submit transactions for approval, or view and complete the approval comment dialog. These configurations help reinforce internal controls, streamline approval chains, and tailor workflows based on organizational needs.

This article explains configuring the *Permissions* tab within the *AWA Approval Record Type Settings*.

### **Configuring Role-Based Permissions for Approval Workflow Automation** <a href="#z63lcax7rii6" id="z63lcax7rii6"></a>

When *AWA* is enabled in *NetSuite*, the **Permissions** tab lets administrators define which roles can cancel approvals, submit records, or see the comment dialog. These options are enabled by default but can be customized to fit internal policies. For instance, you might allow only supervisors to cancel approvals.

Follow the steps below to configure role-based permissions in **AWA**:<br>

1. To open the permission configuration, locate and select the **Permissions** tab within the **AWA Approval Record Type Settings** page:\ <br>

   <div align="left"><figure><img src="/files/Pk9Brdnf84pdpx5DUUSc" alt="" width="563"><figcaption></figcaption></figure></div>

   <br>
2. Next, use the **ALLOW CANCEL APPROVAL** dropdown to decide if users with this role can cancel an approval using the **Cancel Approval** button. This option is enabled by default:\ <br>

   <div align="left"><img src="/files/iyzsafjunVStRozLKYf1" alt=""></div>

   <br>
3. Use the **ALLOW SUBMIT FOR APPROVAL** dropdown to control whether users can submit records for approval. This setting determines if employees can access the **Submit for Approval** button. It is enabled by default:\ <br>

   <div align="left"><img src="/files/lBgZIB7JGJ64dAw39KkG" alt=""></div>

   <br>
4. To control whether users see a comments prompt when approving a record, use the **SHOW APPROVAL COMMENTS DIALOG** dropdown. This setting determines if a dialog box appears when approving through the **NetSuite UI**. This option is also enabled by default:\ <br>

   <div align="left"><img src="/files/zBUp8ls9UStfGB5Ij3zQ" alt=""></div>

   <br>

This concludes the process of configuring role-based permissions for **Approval Workflow Automation**.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.charted.com/ap-automation/charted-configuration/approval-automation/role-permissions-and-approval-controls.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
