> For the complete documentation index, see [llms.txt](https://approval-docs.boloforms.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://approval-docs.boloforms.com/guides/gsuite-add-on/assigning-roles-to-recipients.md). # Assigning Roles to Recipients {% embed url="" %} ### There are **5** different roles available in the BoloForms add-on: * Can Approve- This role is for the recipients that can approve/reject a request. * Get Notification- This role is for the recipients who will get notified only in the process of the approval workflow. (For eg. In a multi-step approval workflow, if a recipient with the Role 'get notified only' is added in step number 2, they'll get notified with the status of the approval of recipient in step number 1.) * Receive PDF- This role is for the people who want to receive a pdf copy for the confirmation of the approval request. * Take Signature- In this role the user has to sign and approve. His/her signature will be visible in dashboard * Acknowledge - In this role user has to acknowledge that they have received this request ### Steps to assign different Roles: 1. From your Google Form, open the add-on. 2. Add a recipient. 3. Click the drop-down menu in front of the 'Role'. 4. Choose the desired role, and click 'Save Settings'

Types of Roles

--- # 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://approval-docs.boloforms.com/guides/gsuite-add-on/assigning-roles-to-recipients.md?ask=&goal= ``` `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.