---
sourceDocument: Zurich Build workflows
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/build-workflows

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Decision tables

# Configuring decision tables {#ariaid-title1}

Release version: Zurich  
Updated July 31, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Workflow Studio is installed automatically with each family upgrade. By updating to the latest version of Workflow Studio, you have the latest updates to decision tables. Configure Workflow Studio and assign roles to your staff based on the permission level they require.

For more information, see [Update to the latest version of Workflow Studio](https://www.servicenow.com/docs/gy43xthtMhm8pzMJUkpg2w "Workflow Studio is automatically installed on your instance. However, Workflow Studio is a ServiceNow Store application, so to get the latest features, you must update your version manually to the most recent version.").

## Decision tables roles and permissions {#ariaid-title2}

Learn about the personas who use decision tables in Workflow Studio, including roles and permissions required for certain tasks.

### Personas {#decision-designer-permissions__section_asz_rdp_4yb}

Review the personas and roles used in decision tables in Workflow Studio.

Decision table admin
:   The decision table admin can create and edit any part of a decision table. The admin may make high-level decisions about when a decision table is needed, create the table, and then pass on the work of authoring the rules
    in the table to someone else. Decision table admins are the only persona who can create inputs and decision table columns and values.

Decision table reader
:   The decision table reader has read-only access to decision tables. They can't add or delete inputs, conditions, or results, but they can export a decision table to Excel.

Decision rule author
:   The decision rule author has the most access to update decision tables after the decision table admin. The admin may create a table with inputs and table columns and then pass on the rest of the work to the decision rule
    author. The decision rule author can add, rearrange, and delete decision rows and edit condition and result values in all rows and columns.

Decision result editor
:   The decision result editor can only edit result values in existing decision rows. The decision result editor may change a value based on a new business decision or policy.

Delegated developer
:   A delegated developer can create, read, edit, and delete decision tables that belong to an application they have delegated developer access to. A delegated developer can't access decision tables in other applications or
    scopes.
{#decision-designer-permissions__table_bvq_s5d_qqb__entry__2}

| Role | Tasks |
|-|-|
| admin and decision_table_admin | Create, read, edit, and delete inputs and decision table columns and values. |
| decision_table_reader | Read-only access to inputs and decision table columns and values. In decision tables, users with this role can export decision tables to Excel. |
| decision_rule_author | Read-only access to inputs and decision table columns. In decision tables, users with this role can do the following: * Add new decision rows * Rearrange decision rows * Delete decision rows * Edit condition and result values in all rows and columns {#decision-designer-permissions__ul_zh1_qnt_q5b} |
| decision_result_editor | Read-only access to inputs, decision table columns, and conditions. In decision tables, users with this role can edit result values in existing decision rows. |
| delegated_developer | Create, read, edit, and delete decision tables in applications that the user has delegated developer access to. |
[Table 1. Decision table user roles and permissions]

{#decision-designer-permissions__table_bvq_s5d_qqb}