Loading...
Please sign in to continue
Recent changes to settings may affect existing risk classifications. Note: This analysis applies globally to all entities/funds.
Manage administrators and members who can access PluralRiskApp.
Grant access, adjust permissions, and keep account administration tidy.
| Display Name | Role | Actions |
|---|
Maintain the funds and management companies that scope the rest of the platform.
Keep naming, type definitions, and operational scopes clean across the app shell.
| Full Name | Short Name | Type | Actions |
|---|
Manage connectors, imports, and exports for the selected entity.
Connect document folders and keep approvals tidy for the selected entity.
Open this panel only when you need to add or update a connector.
Track who still needs to approve access, copy the secure link again, or resend the request without rebuilding the source.
When a SharePoint admin needs to approve access, the request will appear here.
Connect a SharePoint or OneDrive folder to start indexing internal documents for automated sourcing.
Paste a valid risk definition JSON object to create a new risk.
Upload a CSV file with the latest KRI values (Cols: risk_id, kri_name, value, date).
Drag & drop CSV or browse
Download risk definitions for backup or external reporting.
Raw data collections for analysis.
All definitions.
All definitions.
Catalog items.
Review compiler routing, monitor failed knowledge-base automation, and manage retrieval overrides for the selected entity.
Review how the compiler classified internal data inputs, re-evaluate sourcing for the selected entity, and override exceptions when business judgment should win.
These items are currently on the Knowledge Base path but have recent failed automation tasks. Use this list to switch stubborn cases to Human Task or force a KB override explicitly.
Search active data items for the current entity and set exceptions without waiting for a full recompilation.
Run a comprehensive suite of health checks to identify data inconsistencies, broken links, and other potential issues within the KRI, Limit, and Data Hub systems.
Run the safe, entity-scoped repair sequence automatically: audit, consolidate, sync item state, republish follow-up jobs, heal bindings, and reconcile tasks. This flow does not delete orphaned items or trigger LLM recompilation.
This action finds and permanently deletes `data_items` that are no longer referenced by any KRI or Limit. This is useful for cleaning up the database after risks, KRIs, or Limits have been deleted.
Warning: This action is irreversible. It is recommended to run a System Audit first to see how many orphaned items will be affected.
Repair data integrity or perform one-time migrations. Always run a System Audit first.
Review, approve, or reject medium-confidence merge suggestions generated by the nightly deduplication job.
| Confidence | Item A | Item B | LLM Rationale | Actions |
|---|
Drag & drop SVG file
or browse
Usage Count: