Help Centre & Docs

Yes. Prism’s access model includes tenant-configurable OIDC SSO with support for identity providers such as Azure AD, Okta, Google Workspace and other OIDC-compatible providers. For organisations with centralised identity controls, Prism access can sit inside the existing authentication model.

The first access decisions should cover administrator ownership, user roles, SSO requirements, portal-only users, internal user limits, approval authority and who can export or publish sensitive information. Good access setup early reduces rework later.

Portal users should be treated as external-facing, read-oriented users. Their access should be linked to the correct LP or investor relationship and limited to the materials deliberately made available through the Investor Portal.

A better import path reduces the risk that poor setup becomes the first user experience. Field validation, row-level issue handling and clearer templates help make the initial dataset trustworthy enough to support reporting, dashboards, CRM and portal workflows.

Typical early records include organisation and contact data, LP and GP records, fund records, asset records, commitment data, capital activity, document metadata and reporting inputs. The exact order depends on the first workflow selected for rollout.

Integrations should be considered once the internal data model and workflow are clear. Bulk import, API-key ingest, webhooks, exports and BI pathways are useful only if the receiving workflow is already understood.

Reporting should draw from the same fund, portfolio, CRM, commitment, document and workflow context used elsewhere in Prism. That reduces the gap between what the operating system knows and what the report says.

Common export needs include PDF report packs, CSV and XLSX data outputs, print-friendly reviews, audit exports and BI-friendly pathways. The right export depends on whether the output is for internal review, investor communication, reconciliation or downstream analysis.

Investor-facing reports, board packs, sensitive finance outputs and AI-assisted commentary should be reviewed before formal use. Approvals help make the reporting process more accountable and easier to evidence later.

AI should operate under tenant-level configuration, usage controls, provider configuration, audit logging and human review. This keeps AI assistance aligned with the same governance model used for reporting, documents, approvals and data access.

Reporting and AI are connected, but they answer different questions. Reporting explains report packs, templates, sections, exports and review workflows. AI Assistance explains extraction, drafting, portfolio assistant use, controls, usage governance and review boundaries.

No. AI-assisted outputs should be treated as first-pass assistance. Commentary, extracted fields, analysis and summaries should be reviewed by authorised users before being relied on in reporting, investor communication or formal decision-making.

The internal data and reporting foundation should be trusted first. Portal access works best after core records, visibility rules, branding, documents and investor-facing material are already clean.

Tenant branding can support a more polished investor-facing experience through logos, colours, welcome text and branded presentation across portal and stakeholder workflows where configured.

Investor-facing materials should flow from controlled reporting and document workflows into portal availability. That helps reduce unsecured email distribution and gives the manager a clearer record of what was made available.

Useful approval evidence includes who submitted the item, who reviewed it, the decision, timestamp, notes, supporting context and the resulting action. This makes the workflow easier to review later.

Delegation can help keep operations moving when a usual approver is unavailable. Delegated decisions should still remain visible in the approval trail so it is clear who acted and in what capacity.

Governance is strongest when it connects to reporting, portal publication, documents, dealflow, CRM, settings, exports and audit logs instead of sitting in a separate spreadsheet or email thread.

Security reviewers should start with the Security & Compliance page. It gives the clearest single view of Prism’s security posture, access controls, tenant isolation, document controls, audit logging, AI governance, integration controls and deployment security.

Prism’s trust model includes audit logging around significant platform activity, with reviewable audit history intended to support governance, internal review, operational oversight and external diligence.

Document access should be reviewed through the lens of authentication, tenant boundary, role permissions, portal visibility, download logging, watermarking where enabled and whether investor-facing documents are published through controlled workflows.

Private deployment is for organisations that need Prism to run locally, in a private cloud or inside a customer-controlled environment. It is scoped separately because hosting, support, maintenance, security review and environment responsibility vary by organisation.

Tenant branding helps firms present a more controlled experience across the platform, investor portal, login experience and report outputs where configured. It is especially important for stakeholder-facing workflows.

Use the Pricing page for Prism Cloud plan information, seat limits, portal viewer capacity, annual billing, monthly billing and the distinction between standard SaaS pricing and private deployment discussions.

Use the FAQ page for common buyer and user questions. The Help Centre is the documentation hub; the FAQ is better for concise answers around product fit, pricing, access, deployment and practical concerns.

Use the contact route on perspect.finance for commercial, operational, support, diligence or security questions. The purpose of this Help Centre is to make the first answers easier to find, not to block direct support when needed.

Over time, this page can expand into deeper setup walkthroughs, role and permission guides, SSO configuration notes, import templates, reporting instructions, investor portal setup, AI governance guidance, retention guidance, security-review references and administrator checklists.