> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/workflows/designing-workflows/processes/shape-repository/service-task/delegates/addresourcerole-and-removeresourcerole-delegates.md).

# AddResourceRole and RemoveResourceRole delegates

The **AddResourceRole** and **RemoveResourceRole** delegate respectively adds and removes the user as the member with the role to the resource. Matched/removed member is returned with output variable.

| Field name         | Required | Description                                                                                                                  |
| ------------------ | -------- | ---------------------------------------------------------------------------------------------------------------------------- |
| resourceId         | Yes      | Id of the resource for the member.                                                                                           |
| roleId             | Yes      | Identify the member role - either id or name must be set, setting both will cause id to be used.                             |
| roleName           |          |                                                                                                                              |
| userId             | Yes      | Identify the member user - either id or name must be set, setting both will cause id to be used.                             |
| userName           |          |                                                                                                                              |
| resultVariableName | No       | The name of the variable that the result will be set in, if not given the result will be set in the variable named "output". |

The delegate is deprecated. Replace your service task containing this delegate with a script task, for example:

* Add resource role:

  ```
  \<scriptTask id="scripttask1" name="Assign owner" scriptFormat="groovy" activiti:autoStoreVariables="false"\>
      \<script\><![CDATA[
          import com.collibra.dgc.core.api.dto.instance.responsibility.AddResponsibilityRequest
          def userName = execution.getVariable("startUser")
          def ownerUserId = userApi.getUserByUsername(userName).getId();           
          responsibilityApi.addResponsibility(AddResponsibilityRequest.builder()
              .resourceId(item.id)
              .resourceType(item.type)
              .roleId(string2Uuid(roleId))
              .ownerId(ownerUserId)
              .build())
      ]]>\</script\>
  \</scriptTask\>
  ```
* Remove resource role:

  ```
  \<scriptTask id="scripttask1" name="Remove current Owner role" scriptFormat="groovy" activiti:autoStoreVariables="false"\>
      \<script\><![CDATA[
          import com.collibra.dgc.core.api.dto.instance.responsibility.FindResponsibilitiesRequest
          def ownerUserId = userApi.getUserByUsername(ownerName).getId();
          def ownerRoleId = users.getRoleId("Owner");
          def responsibilities = responsibilityApi.findResponsibilities(FindResponsibilitiesRequest.builder()
              .resourceIds(Collections.singletonList(domain.id))
              .ownerIds(Collections.singletonList(ownerUserId))
              .roleIds(Collections.singletonList(ownerRoleId))
              .build())
           .getResults()
          responsibilityApi.removeResponsibilities(new ArrayList(responsibilities.collect{ it.getId() }));
      ]]>\</script\>
  \</scriptTask\>
  ```


---

# 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://developer.collibra.com/workflows/designing-workflows/processes/shape-repository/service-task/delegates/addresourcerole-and-removeresourcerole-delegates.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.