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.
Permission boundaries around every decision
Traceable actions and tamper-evident history
Inside the capability
Connected context, explicit responsibilities.
Know what the view connects, what remains outstanding and who can take the next step.
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
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
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
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
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
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.
- 01
Identify authority
Institution, owner and permitted action.
- 02
Check access
Role and record boundaries.
- 03
Preserve evidence
Use authorised received version.
- 04
Review requirements
Mandatory gates and source status.
- 05
Approve independently
Where required; administration is not approval.
- 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.
Inside the workspace
Records, follow-up and review history.
Explore connected evidence, review history and the work available to authorised teams.
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
How it works in practice
An investigator sees only the permitted case context
- 01
Inputs
An institution receives a frozen customer share and opens a case with sensitive notes.
- 02
Controls & actions
The investigator records evidence and reasons; an independent approver reviews the permitted conclusion. A separate institution cannot browse this private case.
- 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.
Connect the relevant services
Select what your programme needs.
Choose commercial services independently to match your programme. People 360, Business 360 and Reusable KYC are shared platform capabilities. Agree service scope, commercial terms and any required source connections for your institution.
Assignment, evidence, escalation and investigation history.
Higher-risk reviews, funds and wealth evidence, independent conclusions.
Scoped access to selected compliance workflows.
Create and maintain your KYC profile in one secure place, then choose the institution, purpose and information you authorise for each share. Submitted versions stay fixed, and each institution makes its own compliance decision.
Choose specialised modules for your institution’s compliance programme. Connected customer and business records bring evidence, relationships and review history together, with access defined by your selected services and institutional roles.
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.