How to assign Candidate groups, candidate users

[Abhishek_Bajaj]

Hi Camunda community,

How do we set up Candidate groups, candidate users?

I have set up a few groups on the Camunda console → Organisation. But I cannot call them.

[korthout]

Hi @Abhishek_Bajaj and welcome to our forums!

The candidate users field can be either a static value or an expression. Currently, you’ve defined an expression = Approver. To resolve it, a process variable named Approver must exist in the process instance and be visible to the user task. The expression must evaluate to a list of strings. If the variable Approver is not a list of strings but a single string then please adjust the expression to = [Approver].

For more details on specifying candidate users for a user task, refer to the user task documentation.

Typically, the assignee, candidate users, and candidate groups are defined as static values (e.g. some_username , some_username, another_username and sales, operations ), but they can also be defined as expressions (e.g. = book.author and = remove(reviewers, book.author) and = reviewer_roles ). The expressions are evaluated on activating the user task and must result in a string for the assignee and a list of strings for the candidate users and a list of strings for the candidate groups. - source: User tasks | Camunda 8 Docs

For more details about the effects of a user task’s candidate users, refer to the tasklist access-control documentation.

User task access restrictions are enabled by default. To disable them, navigate to Console settings and turn off the Enforce user task restrictions toggle.

When activated, tasks assigned to users or candidate groups are only visible to the assigned user or respective group members. When deactivated, every user can see any task, regardless of the assignment.

This configuration does not affect API users. When retrieving tasks using the APIs, all tasks are returned. - source: User task access restrictions | Camunda 8 Docs

Hope it helps