Classification
Classification lets the organisation attach meaningful handling context that other policy decisions can use.
Governance
Governance should change what the product does.
Policies are useful only when they reach the moment of action. Casewelt is designed to carry governance context with content so sharing, deletion, placement and audit can respond to the rules that actually apply.
CreatedContent enters a workspace
ClassifiedOrganisation labels it
ControlledPolicy evaluates actions
ObservedEvents remain queryable
RetainedKeep, hold or delete
Governance controls
Know what the content is, where it belongs, what may happen to it and how long it must remain.
Placement
Regional placement can be an organisation rule, with conflicting writes surfaced rather than silently rerouted.
Permitted actions
Authorisation separates identity from permission and can restrict sensitive operations such as external sharing.
Evidence
Audit gives governance decisions a durable record that can be queried directly and forwarded to downstream systems.
Retention & hold
Make preservation and deletion deliberate.
Retention is a business rule that defines how long content must remain and when disposition may proceed. Hold adds another constraint: even if ordinary deletion would otherwise be permitted, the product should preserve the object while the authorised hold is active.
The useful behaviour is observable: a governed deletion succeeds when policy permits, fails when a hold blocks it, and leaves enough audit context to explain the outcome later.
See a worked governance examplePrivacy-minded architecture
Support privacy obligations with product controls.
Casewelt is intended for organisations that need to reason about access, retention and regional handling under frameworks such as UK GDPR and GDPR. The product can support those programmes; lawful processing and compliance outcomes still depend on the organisation’s own purposes, policies and operation.
Access that can be limited
Authorisation and share lifetime give the organisation a way to restrict who can act, for how long, and on which object — including ending external access without dismantling staff accounts.
Retention that can be operated
Keep, hold and delete become product states rather than mailbox conventions, so a later review can see why content remained or why deletion was refused.
Placement that can be discussed
Home region as organisation context makes geography a rule you can test, instead of a routing hint that quietly relocates a governed record.
Talk to us
Discuss the governance rules you need to operate.
Bring the labels, retention rules, hold process or regional constraints you already use. We’ll focus on how they should reach the content system.