Status. Proposed design only. Nothing in this vault is DG client approval. No application, service or test has been executed; every scenario is Not executed. Fees and dates are open.
DG27 · Assisted onboarding does not grant impersonation
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Manual DG service |
| Layer / kind | Manual + additional-scope boundary |
| Priority | — |
| Gates | S08 |
| Build step | Step-12-Manual-DG-Services-and-Scope-Guards |
| Decisions | Q19, Q14 |
Given
Owner asks DG for help on a missing field; helper lacks product edit authority or has been revoked.
When
DG explains field/pastes suggested wording into an approved help response; owner reviews and enters it.
Then / oracle
No password request, owner login reuse or DG edit via admin bypass. Separate profile copy, promotion and private evidence permissions. Manual delegation record is not software authority. In-product edit-on-behalf remains additional scope; absent/unknown owner does not auto-approve.
Evidence required
Help request/allowed fields, advice and owner-confirmed version; denied impersonation/edit routes.
Decision dependency (verbatim)
Q19/Q14: helper authority and contact route; any delegation feature needs separate scope.
Source: TDD rev 1.3 (PDF); machine-readable in 10-Sources/tdd-bundle/. Back to Scenario-Index · Traceability-Matrix · integration dependencies in Dependency-and-Regression-Table.