Approvals & Governance
Controlled approval workflows, role-based review, delegation, audit evidence and tenant-level governance for sensitive investment operations inside Prism.
Controlled approval workflows, role-based review, delegation, audit evidence and tenant-level governance for sensitive investment operations inside Prism.
Investment operations depend on decisions that should not happen informally. Deal progression, report approval, investor-facing document publication, capital activity, sensitive data changes, exports, integrations and tenant configuration all need the right people involved at the right time.
Prism is designed to bring those controls into the operating workflow. Instead of relying on email sign-offs, spreadsheet notes or undocumented verbal approval, Prism gives teams a clearer approval and governance model around sensitive actions.
The goal is not bureaucracy. The goal is control with evidence: who submitted the request, who reviewed it, what was approved, when it happened, what changed and how the decision fits into the wider operating record.
The governance problem
Email approvals and informal sign-offs create avoidable control risk
Investment teams often approve sensitive actions across inboxes, meetings, chat messages and spreadsheets. That makes it difficult to prove who approved what, when, why and against which supporting information.
Scattered decisions
Approvals often sit across email chains, chat messages, offline files and meeting notes, making it harder to reconstruct the decision path later.
Unclear authority
When approval rules are informal, teams can struggle to prove whether the right role, committee, finance owner or administrator reviewed the action.
Weak audit evidence
Sensitive workflows need durable evidence. Teams should be able to review the submission, approver, timestamp, decision, notes and outcome in one place.
Approval workflow model
Move sensitive actions through a controlled review path
Prism approval workflows help teams define when approval is required, who should review the action and what evidence should be retained.
Submit
A user prepares a sensitive action, such as a report, document publication, deal update, export or controlled finance change.
Route
The workflow routes the request to the required reviewer, role or approval group based on tenant configuration.
Review
Approvers review the request, context, supporting data and notes before approving, rejecting or requesting changes.
Record
The decision, reviewer, timestamp, notes and outcome can be recorded to support auditability and future review.
Where approvals apply
Governance should sit around the workflows that matter most
Different teams need controls in different places. Prism is designed to support approval workflows across investment operations, reporting, documents, investor communications, integrations and configuration changes.
Deal workflow
Apply approval gates to deal progression, investment review, due diligence milestones and controlled pipeline changes.
Reports
Route board packs, investor updates, quarterly reports and internal finance outputs through review before publication or export.
Documents
Control publication of investor-facing documents, portal materials, uploaded evidence and sensitive files before external access.
Settings and controls
Require review for changes to tenant configuration, permissions, branding, integrations or other sensitive operating settings.
Delegation and continuity
Governance should not stop operations when one person is unavailable
Approvals need control, but investment operations also need continuity. Prism is designed to support practical delegation while preserving reviewability and audit evidence.
Temporary delegation
Where appropriate, approval responsibility can be delegated so time-sensitive workflows do not stall because a usual approver is unavailable.
Role-aware coverage
Governance can be based on roles and responsibility rather than fragile dependence on a single named individual.
Reviewable substitution
Delegated decisions should remain visible in the approval trail, making it clear who acted, in what capacity and when.
Tenant configuration
Governance rules should fit the organisation, not force one rigid process
Different investment teams have different operating models. Prism governance is designed to be configurable at tenant level so administrators can align approval behaviour with the firm’s internal controls.
Workflow rules by action type
Approval requirements can be designed around the action being taken: report publication, document release, deal movement, finance change, configuration update or another controlled workflow.
Controls can be adapted by tenant administrators
Not every workflow needs the same level of formality. Tenant administrators should be able to enable, disable or adjust controls where appropriate, while preserving governance for sensitive actions.
Audit trail and evidence
Make approval decisions easier to review later
Approval workflows are only useful if they leave a clear record. Prism helps teams connect decisions to users, timestamps, notes, supporting data and downstream actions.
Who
Record which user submitted the request, which role reviewed it and who made the final approval decision.
What
Capture what was being approved, including the report, document, deal, setting, export or finance action involved.
When
Preserve timestamps for submission, review, approval, rejection, publication and downstream workflow execution.
Why
Attach notes, context and review comments so later reviewers understand the reasoning behind the decision.
Connected governance
Approvals are stronger when they connect to the rest of the platform
Governance should not sit in a separate spreadsheet. Prism connects approval activity with reporting, documents, deals, CRM context, tenant settings, integrations and audit logs.
Reporting and AI
Investor-facing reports and AI-assisted commentary can remain subject to human review before publication or distribution.
Investor portal
Portal document publication, report availability and investor-facing materials can be managed as controlled external-access workflows.
Integrations
API ingest, webhooks, exports and connected data flows should sit inside the same governed operating model as the rest of Prism.
Prism Cloud or private deployment
Governance controls should travel with the deployment model
Use approvals and governance controls in managed Prism Cloud, or discuss standalone private deployment for organisations that need Prism to operate in a local, private cloud or customer-controlled environment.
Managed governance inside Prism Cloud
Prism Cloud gives teams managed access to approval workflows, audit trails, reporting governance, portal publication controls and tenant-level configuration without operating their own infrastructure.
Governance in customer-controlled environments
For organisations with stricter hosting or data-control requirements, Perspect can discuss standalone deployment so approval and governance workflows operate in a local, private cloud or customer-controlled environment.
Investment operations depend on trust in process as much as trust in data. A report number, document release, deal progression, export or capital action is stronger when the team can show how it was reviewed and who approved it.
Prism’s approvals and governance layer is designed to bring that evidence into the operating system itself. Approval workflows, role-based review, delegation, audit trails, tenant configuration and connected reporting controls help teams reduce informal decision-making without turning every workflow into unnecessary friction.
For finance, operations, compliance and investment teams, that creates a stronger foundation for controlled growth.
See how Prism supports controlled approval and governance workflows
Explore approvals, reporting governance, document publication controls, audit trails and tenant-level configuration in the live Prism demo environment.