Should Q.C. accept and filing require the domain password even when a PIN is set? #2

New Issue

2026-10-19T02:50:12Z

spencerm commented

2026-10-19 02:50:12 +00:00

Every sign-off (submit, send to Q.C., accept, reject, route, file, ITP block signatures, hand uploads, rev-mismatch approvals) takes a PIN or the domain password as the electronic signature.

Built as the default: the PIN is enough everywhere, including Q.C. accept and filing.

To answer: keep PIN for all, or require the domain password for Q.C. accept and for filing.

Plan reference: Q4a in docs/PLAN.md (open questions). Answer here; the build takes the default until then.

Every sign-off (submit, send to Q.C., accept, reject, route, file, ITP block signatures, hand uploads, rev-mismatch approvals) takes a PIN or the domain password as the electronic signature. **Built as the default:** the PIN is enough everywhere, including Q.C. accept and filing. **To answer:** keep PIN for all, or require the domain password for Q.C. accept and for filing. --- Plan reference: Q4a in [docs/PLAN.md](https://gt.pescoinc.biz/spencerm/PacketStation/src/branch/main/docs/PLAN.md) (open questions). Answer here; the build takes the default until then.

spencerm added the decision: Q.C.phase 6 decision: Seth labels 2026-10-19 02:50:12 +00:00

SethD commented

2026-10-26 15:45:53 +00:00

PIN is enough.

spencerm commented

2026-10-27 20:56:15 +00:00

Applied in PR 50: docs/PLAN.md Q4 and docs/SECURITY.md record that the PIN is enough for every sign-off, Q.C. accept and filing included. The build already works this way. Closing.

spencerm closed this issue

2026-10-27 20:56:15 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: spencerm/PacketStation#2