Workspaces & folders
Give teams a clear hierarchy for ongoing work rather than a temporary exchange room.
Platform
One place for files. Separate controls for the risks around them.
Casewelt gives teams a durable place to organise business content, while keeping identity, external sharing, governance and administration explicit. The result is a content system that supports everyday work without flattening every user and every action into the same trust model.
Content workspaceFiles · folders · versionsIdentitySign-in and principals
PolicyAction + resource decisions
SharingExternal trust surface
GovernanceClassify · retain · hold
AuditQueryable record
APIAutomation + events
Workspace
Content with a stable identity.
Folders make content familiar to people. Versions make it precise for systems. Casewelt treats a file version as a concrete object so sharing, policy and audit can refer to what was actually approved — not an ambiguous “latest copy”.
File versions
Keep version identity explicit so downstream decisions can point to known content.
Metadata & policy context
Carry the labels and lifecycle context needed for later decisions on the same object.
Comments on the version
Discussion stays attached to the file version, including mentions of people who already have an organisation identity.
Inbound file requests
Ask someone outside the workspace to upload into a folder, with a time-bound link and mailbox proof before the object is accepted.
Activity and inbox
Staff can follow workspace activity and in-app notices when comments, tasks or inbound uploads occur.
Trust surfaces
Staff, administrators and external recipients use separate access paths.
This separation keeps each surface aligned with its risk. External sharing does not inherit an employee session, and everyday file access remains separate from privileged organisation administration.
Security review can then inspect each path on its own terms: the share surface for recipients, the workspace for staff, and administration for organisation policy.
Staff workspaceAuthenticated work with files and folders
AdministrationOrganisation, policy and security controls
External sharingNamed recipients with time-bound access
Standing workspace
The files remain after the share ends.
A deal room works well for a single transaction. Casewelt is built for content that outlives that moment — it stays classified, remains shareable under policy and stays auditable when someone asks about it later.
That is why version identity, share objects, hold and home region sit next to folders rather than replacing them. Everyday work stays familiar; the decisions around it stay explicit.
Core controls
Use the platform at the depth your evaluation requires.
Secure sharing
Control external access as a first-class object with recipients, version context, lifetime and revocation.
Authorisation
Permission is evaluated per action and per resource. Signing in establishes identity; the requested action still has to pass policy.
Auditability
Keep an authoritative event record that can answer product questions directly.
Lifecycle governance
Apply classification, retention and hold to the content lifecycle.
Developer surface
Automate through documented HTTP contracts and receive signed events.
Regional control
Use organisation-level placement rules and make conflicts explicit.
Evaluate the platform
Walk through one operating model.
Use a real content-security scenario: the people, objects, policy decisions and evidence it requires.