Playbook activity state-mapping permissions

concept australia Updated Sep 10, 2026 1 min read playbook-act-state-permissions.md

User permissions must be assigned to allow agents to complete or skip activities in playbook using activity state mapping.

Can Complete and Can Skip permissions in declarative action client conditions [sys_declarative_action_assignment.list] are determined whenever an activity is fetched based on the following conditions:

Experience Status Record must be defined
Users must have write access on Experience Status Record
Activity State Mapping rule set must exist for Experience Status Table
User must have write access on Experience Status Field for that table
Activity State to Experience Status mapping rule must exist for that corresponding operation:

Playbook Activities Activity State

Can Complete Complete

Skip Skipped

Playbook Activities	Activity State
Can Complete	Complete
Skip	Skipped

If the permissions are not valid, users cannot perform that operation. The corresponding declarative actions that use the Can Complete and Can Skip client conditions will not display.

[Omitted image "declarative-action-state-mapping-permissions.png"] Alt text: Adding Can Complete or Can Skip client conditions to a declarative action

Note: If a user does not have read access on the Experience Status Field of the Experience Status Record, the default activity state will be used instead. The default activity state is the state of the flow powering the activity.

Parent Topic:Playbook activity state mapping

41 lines · 2.3 KB Wrap lines

---
title: Playbook activity state-mapping permissions
description: User permissions must be assigned to allow agents to complete or skip activities in playbook using activity state mapping.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/build-workflows/workflow-studio/playbook-act-state-permissions.html
release: australia
product: Workflow Studio
classification: workflow-studio
topic_type: concept
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [Playbook activity state mapping, Stages and activities, Understanding the playbook components, Build Playbooks, Playbooks, Workflow Studio, Build workflows]
---

# Playbook activity state-mapping permissions

User permissions must be assigned to allow agents to complete or skip activities in playbook using activity state mapping.

**Can Complete** and **Can Skip** permissions in declarative action client conditions **\[sys\_declarative\_action\_assignment.list\]** are determined whenever an activity is fetched based on the following conditions:

-   **Experience Status Record** must be defined
-   Users must have write access on **Experience Status Record**
-   Activity State Mapping rule set must exist for **Experience Status Table**
-   User must have write access on **Experience Status Field** for that table
-   **Activity State to Experience Status** mapping rule must exist for that corresponding operation:

    |Playbook Activities|Activity State|
    |-------------------|--------------|
    |Can Complete|Complete|
    |Skip|Skipped|


If the permissions are not valid, users cannot perform that operation. The corresponding declarative actions that use the **Can Complete** and **Can Skip** client conditions will not display.

\[Omitted image "declarative-action-state-mapping-permissions.png"\] Alt text: Adding Can Complete or Can Skip client conditions to a declarative action

**Note:** If a user does not have read access on the **Experience Status Field** of the **Experience Status Record**, the default activity state will be used instead. The default activity state is the state of the flow powering the activity.

**Parent Topic:**[Playbook activity state mapping](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/playbook-activity-state-mapping.md)