---
id: DFMOD-C7-POS-002
title: "Switching assignment scope/type resets dependent selections safely"
product: web
module: digital-form
type: functional
priority: P1
risk: high
status: draft
automationStatus: planned
sourceRefs:
  tsd: PK141
  tsdSection: C7
  tsdScenario: C7.2
  prd: PK141
  jira: null
automationRef: null
lifecycleStatus: active
lifecycleReason: "AI-generated draft from PK141 TSD C7.2; pending QA review."
lastReviewedAt: null
reviewedBy: null
supersededBy: null
duplicateOf: null
blockedBy: null
preconditionRefs:
  - PRE-DF-cp-editing-form
tags:
  - web
  - digital-form
  - form-modification
  - assignment
  - client-portal
  - pk141
  - staging
---
## Objective
Verify changing assignment scope (channel/employee) or type (all/specific) resets dependent selections and requires valid reconfiguration.

## Preconditions
- See [[PRE-DF-cp-editing-form]]

## Steps
1. Change the scope or type

## Expected Result
- Then previous dependent selections are reset
- And the user must complete a valid reconfiguration before save
- And changing all→specific does not leave the previous all-inclusive logic behind

## Source Traceability
- TSD: PK141
- Section: C7 - Assignment Modification
- Scenario: C7.2 - Switching scope/type resets dependents
- Acceptance Criteria: PRD C.27 Scenario 1-3, C.28 Scenario 1-5, C.29 Scenario 1-5

## Evidence Required
- Dependent selections reset on scope/type change.

## Notes / Gaps
- Specific-without-entity blocking is covered by DFMOD-C7-NEG-003.