[Feature] Define governed public and anonymous Form intake profiles #2

Open
opened 2026-08-01 16:38:36 +02:00 by zemion · 0 comments
Owner

Outcome

Support public Form entry without weakening tenant isolation, abuse controls, provenance, privacy, or later identity linking.

Decisions required

  • Which profiles are supported: authenticated public account, invitation/token, pseudonymous, or fully anonymous.
  • Required assurance, CAPTCHA/rate-limit/abuse controls, duplicate-submission policy, and token lifetime.
  • Whether and how a later authenticated identity may claim or link a submission.
  • Data-minimization, draft retention, deletion, legal hold, receipt disclosure, and support/recovery rules.
  • Which services may enable each profile and which Policy authority approves it.

Acceptance criteria after decisions

  • Each definition/service selects an explicit profile; no installation-wide implicit anonymous mode exists.
  • Start, draft, submit, receipt, and recovery paths are tenant-bound and replay-safe.
  • Secrets/tokens are hashed or delegated to the appropriate trust owner and never logged.
  • Public APIs expose bounded errors and do not disclose account, tenant, schema, or submission existence.
  • Accessibility, privacy, abuse, expiry, replay, ownership-linking, and recovery tests cover the selected profiles.
## Outcome Support public Form entry without weakening tenant isolation, abuse controls, provenance, privacy, or later identity linking. ## Decisions required - Which profiles are supported: authenticated public account, invitation/token, pseudonymous, or fully anonymous. - Required assurance, CAPTCHA/rate-limit/abuse controls, duplicate-submission policy, and token lifetime. - Whether and how a later authenticated identity may claim or link a submission. - Data-minimization, draft retention, deletion, legal hold, receipt disclosure, and support/recovery rules. - Which services may enable each profile and which Policy authority approves it. ## Acceptance criteria after decisions - Each definition/service selects an explicit profile; no installation-wide implicit anonymous mode exists. - Start, draft, submit, receipt, and recovery paths are tenant-bound and replay-safe. - Secrets/tokens are hashed or delegated to the appropriate trust owner and never logged. - Public APIs expose bounded errors and do not disclose account, tenant, schema, or submission existence. - Accessibility, privacy, abuse, expiry, replay, ownership-linking, and recovery tests cover the selected profiles.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-forms-runtime#2