⚠️ OpenSpec-managed issue — this content is automatically synced
from the openspec/ directory. Manual edits will be overwritten on next sync.
Artifacts
Summary
A supplier or a municipality publishes a compliance document about a product (a DPIA, a processing agreement, a pentest report, an assurance report or a certificate) and says who may read it: everyone, every government organisation in the catalogue, or named organisations. Other municipalities find the documents on the product's page and reuse them instead of asking the supplier for the same paperwork again. Each document carries its type, its date and how long it stays valid.
Specs
Tasks
Design
See design.md for technical design details.
Synced from openspec/changes/sharing-compliance-documents by OpenSpec workflow
App: stackiq
Artifacts
Summary
A supplier or a municipality publishes a compliance document about a product (a DPIA, a processing agreement, a pentest report, an assurance report or a certificate) and says who may read it: everyone, every government organisation in the catalogue, or named organisations. Other municipalities find the documents on the product's page and reuse them instead of asking the supplier for the same paperwork again. Each document carries its type, its date and how long it stays valid.
Specs
Tasks
tests/Unit/Settings/ComplianceDocumentsFragmentTest.php,tests/Unit/Settings/SchemaRbacTest.phpcases for the three audiences)tests/e2e/workflows/compliance-documents.spec.ts, including an organisation outside a named share)Design
See design.md for technical design details.
Synced from
openspec/changes/sharing-compliance-documentsby OpenSpec workflowApp:
stackiq