---
title: "Using workflow parameters to create reviewer teams in a space"
canonical: "https://support.appfire.com/space/CDML/650316136/Using%20workflow%20parameters%20to%20create%20reviewer%20teams%20in%20a%20space"
format: markdown
---
> Macro (aura-html)


## Overview

> Macro (excerpt)
> 
> Using workflow parameters to create teams of users for use in approvals

You can use [workflow parameters](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649760641) to create teams of users.

![image](media://941277e1-0c8b-4f68-9d7c-44a6e4774c54)

You can use these, for example, in approvals, to manage your reviewers.

![image](media://c1e9ea53-3796-4fbb-bd48-684e87aae081)

A space administrator can manage the values of the [workflow parameters](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649760641) in the space tools [Parameters dashboard](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649726501), which are used by an applied space workflow.

![image](media://8c2788df-ba72-4578-a6da-0b12bed8a97e)

Changes made by a space administrator by editing the values in the [Parameters dashboard](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649726501) are used when a workflow is first applied to content in the space. The workflow does not retrieve an updated space parameter value unless an appropriate workflow event takes place.

A workflow author can use a workflow parameter (set as either a **user** or **group** type) to allow their workflow to be used across multiple spaces by different teams of users

- The workflow parameter values for the Confluence users or groups can be edited by the space administrator for each space
- Changes made by the space administrator to the workflow parameter values will be used when adding the workflow to a document.

## Multiple team reviews in a state

You can [add multiple reviews](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649859269) in a state and use each approval to assign different users using the workflow parameters.

For example, using the workflow builder, add three reviews: **Design**, **Technical,** and **Quality,** in the state** Product Review**.

![image](media://0c42e27b-eaa2-436a-94ff-a8e9d3420742)

This creates the following markup in the markup editor.

```plaintext
{workflow:name=Using Workflow Parameters for Team Approvals}
   {state:Product Development|submit=Product Review}
   {state}
   {state:Product Review|approved=Approved|rejected=Product Development}
      {approval:Design|description=Design approval team}
      {approval:Technical|description=Technical approval team}
      {approval:Quality|description=Quality Lead to be assigned for final approval}
   {state}
   {state:Approved}
   {state}
{workflow}
```

## Workflow parameters for the review teams

We can create three workflow parameters, one to manage the reviewers for each approval.

![image](media://5a0408e9-c536-4db3-94aa-8ff0e8681b7a)

In our example, the **Design Team** parameter is a user parameter and has a default value of two users.

```plaintext
{workflowparameter:Design Team|description=Design team members who must approve|type=user}
        matilde,suni
{workflowparameter}
```

Adding a default value for a workflow parameter when creating the workflow adds the workflow parameter to the space tools **Parameters** **dashboard** in the space where the workflow is added.

The second workflow parameter, **Technical Team, **is also a user-type parameter.

![image](media://b86edd06-1f00-4664-b2b7-ba7586e438fc)

The third workflow parameter, **QA Reviewers**, is added as a group parameter. Its value is going to be one or more Confluence groups.

![image](media://6e0e4076-f89c-4712-90db-8b229fa227b3)

In our example, the default value is set as two Confluence user groups in our instance.

These Confluence user groups are

- `project-alpha-leads` that is specific to the project and the space
- `project-quality-leads,` that is a cross-project quality group

## Adding the team parameters as reviewers

Approvals can use the workflow parameters (a value reference) to set the reviewers for each approval.

For the **Design **approval, the Design Team workflow parameter is used to mandate the reviewers who must undertake the approval.

![image](media://bff6a404-1cee-47d4-b644-f65a854d1e98)

The **Technical** approval uses the **Technical Team** workflow parameter to mandate reviewers.

![image](media://24525db1-6290-408e-983a-b34ca578b302)

The **Quality** approval limits the assignment to one approver. The **Quality Team** workflow parameter is used to specify the list of reviewers from which the reviewer can be chosen.

![image](media://fd6c0147-d4c6-4a5f-9221-461e949a5e94)

The **Quality** approval also excludes any users from being assigned who have been mandated to undertake either the **Design** or the **Technical** approval using the same workflow parameters added to these two approvals.

In our example, the Design and Technical approvals in the **Product Review** state are populated with the avatars for the mandated reviewers.

![image](media://f02f19b2-b1e2-474d-8b32-5fbd23edfb9a)

These reviewers are the user values for the workflow parameters **Design Team** and **Technical Team**.

The assignment reviewer for the **Quality** approval is limited to members of the Confluence user groups added as values for the **QA Reviewers** workflow parameter

![image](media://f9d13b00-9e19-458b-9002-db7032fec8e5)

The space administrator chooses the Confluence groups for the value of the **QA Reviewers** workflow parameter in the space.

The membership of the groups is managed by the global administrator:

- `project-quality-leads`
  
- `project-alpha-leads`

> Macro (inline-media-image)

  
  
In the example, user **Elle Bracus** is not available for assignment to this approval, as they** **are also a **Technical Team** workflow parameter user value, and this workflow parameter is used with the [exclude parameter condition](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649662337) for the approval to prevent a user from being assigned.

## Managing the space workflow parameter values

When a workflow is added to a space and contains a workflow parameter with a default value, the workflow parameter and default value is added to the space tools Parameters dashboard.

![image](media://4848529a-1fe8-4d82-9b59-e39e7d2b1bfe)

The values in the dashboard are used by the workflow containing the workflow parameter on the first application of the workflow to content.

For a space the space administrator can choose the

- Reviewers for the **Design** approval by editing the users for the **Design Team** workflow parameter
- Reviewers for the **Technical** approval by editing the users for the **Technical Team** workflow parameter
- Confluence user group(s) (if available) for the **QA Reviewers** workflow parameter. This provides the list of group members who can be assigned as the approver for the **Quality** approval

Editing the workflow parameter value in this dashboard will not change the value used by a workflow that is already applied to content. The new value will only be used when the workflow is initially applied.

> ⚠️ When a workflow is first applied to content, the content is considered as "**unprocessed pages**", and the workflow parameter value might not be available until after a workflow process (such as a transition) has occurred.
> ⚠️ 
> ⚠️ A space administrator can choose to **[Initialize states](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649827807)**** **on the first application of the workflow. This action causes the page to become "**processed**" and the workflow parameter value is updated.
> ⚠️ 
> ⚠️ Alternatively, the workflow author can include an initial state that does not utilize any workflow parameter value. A transition from the initial state will "**process**" the page and update the workflow parameter value.

##   
Example workflow markup

The example workflow contains the following markup 

```plaintext
{workflow:name=Using Workflow Parameters for Team Approvals}
	{description}
   		An approval workflow with 3 states. The Product Review state has 3 approvals.
    {description}
    {workflowparameter:Design Team|description=Design team members who must approve|type=user}
        matilde,suni
    {workflowparameter}
    {workflowparameter:Technical Team|description=Technical team members who must approve|type=user}
        simone,elle
    {workflowparameter}
    {workflowparameter:QA Reviewers|description=Quality leads|type=group}
        project-alpha-leads,project-quality-leads
    {workflowparameter}
   {state:Product Development|submit=Product Review}
   {state}
   {state:Product Review|approved=Approved|rejected=Product Development}
      {approval:Design|user=&@Design Team@|description=Design approval team}
      {approval:Technical|user=&@Technical Team@|description=Technical approval team}
      {approval:Quality|exclude=@Design Team@,@Technical Team@|selectedapprover=@QA Reviewers@|description=Quality Lead to be assigned for final approval}
   {state}
   {state:Approved}
   {state}
{workflow}
```

## See also

[Workflow Authoring Guide](https://appfire.atlassian.net/wiki/spaces/CDML/pages/648611901)

- [Parameter References](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649760641)
- [Editing workflow parameter using workflow builder](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649792431)
- [Approvals](https://appfire.atlassian.net/wiki/spaces/CDML/pages/650153766)
- [Example - Adding Multiple Reviews](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649859269)

[User Guide](https://appfire.atlassian.net/wiki/spaces/CDML/pages/648907144)

- [Content reviews](https://appfire.atlassian.net/wiki/spaces/CDML/pages/650313809)
- [Conditions](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649694110)

[Reporting Guide](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649070833)

- [Workflow Report Macro - Approvals](https://appfire.atlassian.net/wiki/spaces/CDML/pages/650120822)