Workspaces

A workspace is the container in BNDRY that groups the forms, files, and entity links for one piece of customer work — an onboarding, a periodic review, an enhanced due diligence pass, or a remediation. Each workspace has a display name, a state, a creation time, and an optional set of entities it relates to. Workspaces are the top-level unit of work that internal staff act on inside the BNDRY app, and the unit that external customer users see when they follow a magic link into the portal.

Why workspaces exist

Compliance work is almost never a single form. A new customer onboarding might need an identity verification, a source-of-funds declaration, a beneficial-ownership form, and a handful of supporting documents — gathered over days, sometimes weeks, often from more than one person. The workspace exists so that all of those artefacts have one home, one state, and one audit trail. Without it, BNDRY would be a collection of disconnected form responses with no shared context, and reviewers would have to reassemble the picture every time.

The workspace is also the unit BNDRY uses to grant external access. When a customer needs to complete forms or upload documents, the workspace — not an individual form — is what gets shared, typically through a time-bound magic link. This means scope, expiry, and audit are all tracked at one consistent level.

Key properties and sub-types

A workspace carries a small, deliberately stable set of properties:

• Display name — a human-readable label, typically describing the work and the customer it relates to.
• Form definitions — the templates used to create the workspace's initial set of forms. This is set when the workspace is created and is immutable afterwards; the resulting form instances are mutable.
• Entities — the individuals, companies, or trusts the workspace relates to, linked by reference.
• State — the lifecycle phase the workspace is currently in (see below).
• Timestamps — create, update, delete, and purge times; workspaces are soft-deleted before they are purged.

Workspaces move through a small set of lifecycle states:

• To do — awaiting action; typically the state on creation.
• In progress — work is actively being performed.
• Attention — the workspace needs review or intervention.
• Resolved — the work is complete.
• Cancelled — the work was stopped without being completed.

State changes are explicit operations rather than automatic side-effects of form submission, so that the lifecycle of the workspace is owned by a person and visible in the audit trail.

How workspaces relate

A workspace is the parent of one or more forms. Forms can also exist outside a workspace, but inside a workspace they share its access, its state context, and its audit story. Files uploaded against a workspace's forms are listed at the workspace level too.

A workspace optionally references one or more entities — individuals, companies, or trusts already known to BNDRY — so reviewers can see at a glance who the work concerns and so the responses can later be reconciled with the entity record.

External access to a workspace is granted through the portal, typically via a magic link generated for a specific email address with a configurable expiry between one hour and seven days. The link can be scoped to the whole workspace or to a chosen subset of its forms.