Skip to main content
Home/Governance
Governed by design

Put controls inside the workflow, not around the edges.

Hamachi is designed to help wealth firms manage access, firm guidance, review expectations, sensitive data, and workflow evidence as part of the experience people use.

Control model

Govern context, capabilities, and action.

The right controls depend on the task, user, data, system, and consequence, not simply on whether AI is present.

01

Identity and access

Define who can access data, applications, tools, agents, workflows, and actions according to configured roles and responsibilities.

02

Policy and guidance

Bring approved firm instructions, communication guidance, review expectations, and escalation paths into the relevant point of work.

03

Data safeguards

Apply appropriate handling and visibility controls to sensitive information based on the firm’s requirements and implementation.

04

Human oversight

Configure when work can proceed automatically, when a person must review it, and who owns the final decision.

05

Workflow evidence

Preserve relevant state, inputs, outputs, decisions, approvals, and actions so work can be reviewed in context.

06

Change discipline

Manage modifications to prompts, skills, policies, workflows, tools, and integrations through the firm’s chosen process.

Privacy before the model

Create a boundary between client identity and model reasoning.

Hamachi can identify and anonymize sensitive information before model interaction, preserve the context required for the task, then restore the appropriate information inside the governed workflow.

01DetectIdentify sensitive client information
→
02AnonymizeReplace PII before model interaction
→
03ProcessReason with protected context
→
04RestoreReturn authorized context to the workflow
→
05Review + auditKeep people and evidence in the process
PII protection can apply across supported chat, CRM, mailbox, meeting, app, agent, and workflow experiences. Exact handling depends on the configured integration and workflow.
Supervision in practice

Make review and evidence part of the action.

Governance becomes useful when it appears at the point a draft, analysis, recommendation, record update, or external communication could become consequential.

Approval queueThree items require review
EMClient follow-up emailCommunication guidance applied · PII protectedReview
CRCRM household updateFour proposed field changes · source attachedApprove
PLRetirement comparisonDeterministic calculation · assumptions visibleReview
Filter by date, user, workflow, or eventFull activity history →
Risk-sensitive workflow design

Match control to consequence.

A useful governance model distinguishes assistance from recommendation, and drafting from action.

Context and research support

Show source context and boundaries so users can assess relevance, recency, and authority before relying on an output.

Drafting and preparation

Mark generated work clearly and route it through the appropriate person before it becomes an external communication or record.

Analysis and calculation

Use deterministic methods for repeatable calculations, keep assumptions visible, and reserve professional judgment for accountable humans.

System action

Control tool access, validate required inputs, apply approval gates, and preserve the relevant outcome and actor.

Shared responsibility

Technology supports the firm’s program.

Hamachi can provide configurable controls and workflow evidence. Each firm remains responsible for its policies, supervision, legal and regulatory obligations, implementation choices, and use of the platform.

Capabilities, data handling, deployment architecture, and available controls depend on the selected configuration and should be evaluated against the firm’s requirements.
Practical questions

What should a firm decide before launch?

Who can do what?

Define roles, access, workflow ownership, tool permissions, approval authority, and exception handling.

What requires review?

Classify use cases by consequence and determine the appropriate human decision point for each.

What evidence is needed?

Identify the data, workflow events, versions, approvals, and outcomes that should be retained for internal review.

Design governance with the work

Map controls to a real workflow.

We’ll walk through the data, users, decisions, review points, and actions involved in one of your priority use cases.