Skip to content
Lotus Comply

Lotus Comply / Platform & governance / Security & Governance

Protected records. Defined roles. Accountable decisions.

Separate institutional information, limit actions by role and preserve evidence-linked history. Governance controls give authorised teams a clear record of responsibilities, evidence and decisions.

Security & Governance / connected context

Permission boundaries around every decision

Customer ownerPrivate evidence and defined shares
Named, scope-limited frozen shares
Institution AIts permitted records and review roles
Separate private records
Institution BSeparate information and decisions
Audit historyRecorded actions and tamper evidence

Traceable actions and tamper-evident history

Conceptual diagram · permitted records and enabled services

Inside the capability

Connected context, explicit responsibilities.

Know what the view connects, what remains outstanding and who can take the next step.

01

Institution administrator

Keep institutions’ information separate

Institution-specific access boundaries protect private records. A shared customer profile does not merge banks’ investigation files or grant one institution access to another’s decisions.

  • Institution-limited access
  • Named owner-authorised shares
  • No cross-institution private record browsing
02

Governance owner

Separate administration and approval

Role permissions determine who can prepare, review, approve or investigate. Administrative access alone does not confer authority to approve compliance outcomes.

  • Least required operation scope
  • Independent checker where required
  • Guarded status transitions
03

Records officer

Protect received evidence versions

Authorised snapshots and historical assessments stay fixed. Later profile changes support new reviews; lawful retained institution-held records remain separate from future-access consent removal.

  • Frozen point-in-time shares
  • Replacement and review history
  • Retention responsibilities agreed by institution
04

Audit reviewer

Make actions traceable

Recorded actions and a tamper-evident audit chain support investigation of who did what and why. Access, retention and security arrangements are agreed for your institution.

  • Evidence-linked reasons
  • Actor and action history
  • Institution-specific retention controls
05

Compliance reviewer

Keep required checks from becoming false passes

Provider observations inform the workflow but do not establish final clearance. A required missing check, source outage or unresolved candidate stays visible for remediation or review.

  • Observation distinct from decision
  • Technical hold not rejection
  • Independent final authority
06

Case investigator

Restrict sensitive investigation information

Control evidence and sensitive notes according to role and privacy requirements, including tipping-off restrictions. Reporting preparation remains internal workflow, not certified official filing.

  • Restricted notes
  • Reasoned escalation and closure
  • Case-linked approval before internal export

Start to finish / Security & Governance

A clear route, including the exceptions.

  1. 01

    Identify authority

    Institution, owner and permitted action.

  2. 02

    Check access

    Role and record boundaries.

  3. 03

    Preserve evidence

    Use authorised received version.

  4. 04

    Review requirements

    Mandatory gates and source status.

  5. 05

    Approve independently

    Where required; administration is not approval.

  6. 06

    Record & retain

    Reasons, action history and institutional retention.

Authorised action

Permitted role and resolved gates support the next step.

Independent review needed

Return, clarify or escalate with recorded reasons.

Denied / technical hold

Access denial and source outage remain separate from customer rejection.

Example process. Authority, selected services, mandatory evidence and required-source availability determine the permitted next step.

Inside the workspace

Records, follow-up and review history.

Explore connected evidence, review history and the work available to authorised teams.

Lotus Comply / Security & Governance
Sample record

Permission boundaries around every decision

Sample review context
Access boundary
Institution-specific records
Decision authority
Reviewer + independent approver where required
Audit chain
Tamper-evident action history
Source outage
Technical hold · not clearance
Example workspace · Sample data

How it works in practice

An investigator sees only the permitted case context

  1. 01

    Inputs

    An institution receives a frozen customer share and opens a case with sensitive notes.

  2. 02

    Controls & actions

    The investigator records evidence and reasons; an independent approver reviews the permitted conclusion. A separate institution cannot browse this private case.

  3. 03

    Outcome & exceptions

    Actions remain attributable and role-limited. Customer updates do not rewrite the case’s received evidence, and consent removal does not erase lawful retention.

Questions & answers

Before you choose Security & Governance.

Is the audit chain certified WORM?

The audit chain provides tamper evidence and traceable actions. It is not certified WORM storage; discuss current security documentation and retention requirements with the team.

Can an administrator approve everything?

No. Administrative functions are separate from defined compliance decision authority and independent-review requirements.

Is a provider hold a customer rejection?

No. It is an unresolved technical requirement that needs authorised retry or remediation, rather than a customer decision.

Connect the work. Keep authority clear.

Discuss your requirements