Content before category
Start with the files, people and decisions that need control rather than forcing every requirement into a fashionable product category.
Approach
If a file is refused, frozen or stopped, you see why.
The decision happens in the product, with a reason attached.
Boundaries before slogans
Your staff, your administrators, the people you share with and the systems you connect are four different risks. We keep them four different things.
Controls you can operate
Nothing is allowed unless a rule says so. Every file version has its own key. Sessions can be ended on the spot. The record is added to, never rewritten. All of it is in the product, not bolted on afterwards.
Where Casewelt fits
Standing organisational content, with security and governance attached.
Casewelt is designed for ongoing organisational work rather than only a short-lived transaction room. External sharing matters, but it is one controlled capability around a broader content workspace.
The product also does not depend on being the organisation’s only identity provider, office suite or automation platform. It should work alongside those systems while keeping responsibility for content authorisation, sharing, lifecycle and audit clear.
Product boundaries
Where Casewelt draws the line.
Standing workspace
A deal room works for a single transaction. Casewelt is built for content that continues before, during and after that moment, with classification, policy and audit still attached.
Alongside the office suite
People can keep creating files in the tools they already use. Casewelt is where those files become governed objects with policy, sharing and audit attached.
Identity provider
Identity remains with the organisation’s identity provider. Casewelt consumes those principals and applies product policy to their actions.
Design choices
What we care about when we build.
Things you can name later
A file, a version, a share and a policy decision each keep a stable identity, so you can point at them months afterwards.
Refusals you can see
When policy, hold or placement says no, the product stops the action and leaves a clear reason, not a quiet failure in a log.
Outside access that stays narrow
Recipients get a time-bound door to a document. They do not borrow an employee login or see a workspace.
Evidence you can search
Important events stay in a structured record you can query, not only in someone’s inbox.
Fits what you already run
OIDC, APIs and signed events connect Casewelt to the identity provider, SIEM and systems you already operate.
Claims that match the product
Public wording should not outrun what the product can show, especially for security and compliance.
Evaluate
Bring your own scenario.
A feature list is less useful than one real file and the rule that must not break. We will walk the controls around that path with you.