Controlled Client Access

Why Controlled Client Access Matters

Client communication should not require opening the firm’s private workspace. A recipient needs a clear way to inspect the material expressly shared with them and understand what it is.

Staff need to decide which exact content can be disclosed, to whom and for how long. A general folder link cannot replace source rights, confidentiality checks or review of the selected version.

The client portal provides a separate named-recipient workflow where enabled for an agreed deployment. It keeps explicit disclosure decisions distinct from internal export and from staff membership.

How It Works

Establish named recipient access

Use a dedicated recipient identity and the authorized access workflow. Portal participation is separate from staff accounts and does not open the general Matter workspace.

Prepare the selected content

Choose the exact internal material or permitted artifact and the intended recipient. Inspect source rights, confidentiality and expiry before advancing the disclosure workflow.

Review before sharing

Use the available independent review and explicit sharing controls for the selected version. Exporting a file or preparing a bundle does not itself send it to a recipient.

Receive scoped supporting input

Where available, a recipient can use the question or file controls attached to a current reviewed disclosure. Staff must separately accept, scan and review incoming material before it supports Matter work.

The Difference

Without a scoped recipient workflow

With deliberate client disclosure

Client access relies on broad folder links.

Use a dedicated named-recipient workflow.

Shared versions are difficult to identify.

Bind disclosure to selected reviewed content.

Internal export is assumed to mean delivery.

Inspect rights and confidentiality before sharing.

Recipient expiry is separated from the content.

Apply current recipient access and expiry.

Incoming files are treated as established evidence.

Review received input before Matter reliance.

Built for Deliberate Recipient Disclosure

A recipient can inspect material specifically shared under their current access.

A staff member can distinguish preparation, review and explicit disclosure.

Incoming supporting material retains a separate acceptance and evidence-review path.

See Controlled Client Access in Action

Review the workflow with representative synthetic records and the roles your firm intends to use.

Ronni K. Gothard Christiansen - Technical Privacy Engineer & CEO

Technical Compliance Expert, 32+ Years Open Source Advocate, X-BoD Open Source Matters Inc.

Or contact via

ronni@aesirx.io +84 909 500 760

Frequently Asked Questions

The portal uses dedicated recipient access. It does not convert a recipient into a staff member or grant general access to the firm’s private Matters and library.

Internal export and disclosure are separate actions. Staff must select the permitted content and named recipient, satisfy review and rights requirements and explicitly share it through the available workflow.

Where enabled, question and file controls belong to a current available disclosure. Without an available disclosure those controls may be absent; staff must separately accept, scan and review submitted material.

Revoking access can block later portal access, but an earlier download cannot be recalled from a recipient. Staff should inspect the content, audience, rights and expiry before sharing.

An evaluation demonstration does not authorize actual client material. The firm must confirm deployment scope, recipient provisioning, source rights, security and its required approvals before a real-client rollout.

Next Steps

Start a Compliance Pilot

Discuss the deployment, audience and source-rights requirements for an agreed evaluation.

Discuss Your Compliance Needs

Discuss how your firm could share reviewed material securely with named client recipients.

Controlled Client Access | AesirX