> For the complete documentation index, see [llms.txt](https://help.form.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.form.io/form-building/actions/role-assignment-actions.md).
# Role Assignment Actions
Setting up a form action to add, modify, or remove a role associated with a submission
The **Role Assignment Action** adds, modifies, or removes roles associated with the submission when an event occurs on a form. A common use case for the Role Assignment action is adding the action on a Registration form to grant users certain roles after they register. Those roles will then work in tandem with Form.io's authentication system.
## Settings
**Resource Association:** The resource association will determine if a new or existing resource will be modified.
**Action Type:** What type of role assignment action to take.
Add Role: Adds the given Role to the submission record.
Remove Role: Removes the given Role from the submission record.
**Role:** The role to use when performing the role assignment. Roles are managed from the Access section of the project found on the left-hand navigation bar.
{% hint style="info" %}
The Role Assignment Action requires a Resource Form component with the API key, ‘submission’, to modify existing Resource submissions
{% endhint %}
## Video
{% embed url="" %}
---
# 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.form.io/form-building/actions/role-assignment-actions.md?ask=&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.
