An assignee of a role may accept the role. By doing so, this assignee takes responsibility for completing all of the role's tasks. If this assignee later realizes that s/he has insufficient time or expertise, and wishes to allow another assignee of the role to accept that responsibility, then s/he may refuse the role.
Accepting a role has several benefits.
Suppose that a role has several assignees (e.g. the 3 members of the Accounts Payable Department). Until one of the assignees accepts the role, all of the assignees see the role's tasks in their My Assignments lists. After one of the assignees accepts the role, only this user sees the role's tasks in his My Assignments list, because he has accepted responsibility for completing these tasks. The other assignees still have the same access as before, but they are not involved in completing the role's tasks.
Suppose that the process owners want to know whether the assignee of a role is aware of that role and is willing and able to do the work. When the assignee accepts the task, the process owners know that the assignee is aware of the role and the tasks, and has accepted the responsibility for completing them.
An assignee who has accepted the role may subsequently refuse the role, indicating that s/he is no longer able/willing to perform the role.
How does a user accept a role?
How does an assignee accept a role?
An assignee may accept a role in the following ways:
Explicitly accept the role, using the Role Assignees popup.
Complete a task that is assigned to the role.
Start a task that is assigned to the role.
Reopen a task that is assigned to the role.
How does an accepting user refuse a role?
An assignee may refuse a role in the following ways:
Explicitly refuse the role, using the Role Assignees popup.