Project task hierarchy and permissions in CWM

  • Release version: Australia
  • Updated July 23, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Project task hierarchy and permissions in CWM

    This content explains how assignee status, hierarchy rules, and item-type conditions govern the creation, movement, and association of Cloud Workflow Management (CWM) child tasks and stories under project tasks in ServiceNow's Project Workspace. It clarifies who can add or move CWM items on a Board, when such actions are allowed, and how restrictions are communicated within the user interface.

    Show full answer Show less

    Key Features

    • Assignee Permissions: Only users assigned to a project task—either directly in the Assigned to field, as a resource assignee, or via a resource assignment group—can successfully create, indent, or drop CWM child tasks or stories under that task. Non-assignees see options but receive an error notification if they try to add items.
    • Hierarchy Restrictions: Project tasks that already have child project tasks cannot accept additional CWM child tasks. This restriction applies to all users, including assignees. The Board’s Project task dropdown excludes such project tasks to prevent selection as parents for new CWM items.
    • Item-Type and Phase Type Conditions: Both "Add child CWM task" and "Add child story" options appear on all project tasks, regardless of phase type. However, on non-agile phases, only adding child tasks succeeds; attempts to add child stories result in error notifications.
    • Restriction Signals on the Board:
      • Error notifications appear inline for non-assignees attempting restricted actions.
      • Dropdown menus exclude project tasks that cannot accept children.
      • Inline notifications inform users when a project task already has child tasks and cannot accept more.

    Practical Implications for ServiceNow Customers

    • Understanding assignee roles ensures proper delegation and control over who can manage CWM child tasks and stories under project tasks.
    • Hierarchy enforcement maintains project task structure integrity by preventing mixed child types under the same parent task.
    • Phase-type-based restrictions allow customers to align task creation capabilities with their project methodologies (agile vs. other types).
    • Clear user interface signals help reduce errors and guide users on permissible actions within Project Workspace Boards.

    Learn how assignee, hierarchy, and item-type conditions determine which project tasks accept CWM children and who can add or move them on a Board.

    Adding or moving a CWM task or story under a project task is subject to assignee, hierarchy, and item-type rules. These rules determine which context menu options appear, which project tasks are available in the Project task column dropdown, and whether an action completes or displays an inline notification.

    Project task assignees

    A user counts as an assignee of a project task when at least one of the following is true:

    • The user is listed in the Assigned to field on the project task.
    • The user is listed as a resource assignee on the project task.
    • The user is part of a resource assignment group on the project task.

    Only assignees can create, indent, or drop CWM items under a project task. The Add child CWM task and Add child story options still appear for non-assignees, but selecting one displays an inline error notification instead of creating the item.

    Hierarchy restriction on CWM child tasks

    A project task can't accept CWM child tasks when the project task already has child project tasks. This rule applies to all users, including assignees. To see the existing child project tasks for a project task, open it in Project Workspace.

    The Project task column dropdown on a Board excludes project tasks that already have child project tasks. So, those project tasks can't be selected as a new parent when a CWM item is moved.

    Child task and story creation availability

    Both the Add child CWM task and Add child story options appear on every project task, regardless of its phase type. Whether the action completes depends on the phase type:
    • On an agile project phase, both Add child CWM task and Add child story complete successfully.
    • On a project task with any other phase type, only Add child CWM task completes. Selecting Add child story displays an error notification instead of creating the story.

    Restriction signals on the Board

    Restrictions are surfaced in one of three ways, depending on the rule and the action:

    Error notifications for non-assignees
    For non-assignees, the Add child CWM task and Add child story options still appear, but selecting one displays an inline error notification instead of creating the item.
    Dropdown exclusions
    While associating a CWM task with a project and project task, the Project task column dropdown shows only those project tasks that don't already have child project tasks.
    Inline notifications
    If a project task already has child project tasks, then you can't associate additional CWM tasks or stories.