Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/AllianceBioversityCIAT/onecgiar_pr/llms.txt

Use this file to discover all available pages before exploring further.

PRMS is a reporting and management platform, not a standalone data island. It connects to a set of external systems to source authoritative data, verify identity, store files, deliver messages, and provide a real-time user experience. None of these systems are owned or operated by PRMS — it integrates with them. This page gives you a map of every external connection and what it means for you as a user. For the three most significant integrations, dedicated pages go into greater depth.

Integration map

CLARISA

The authoritative catalog of CGIAR institutions, centers, initiatives, countries, regions, SDG targets, impact areas, and indicators. Every partner dropdown, center picker, and SDG selector in PRMS is sourced from CLARISA via a scheduled sync. PRMS is a read-only consumer.

Theory of Change services

External ToC management systems that hold each Initiative’s impact pathways and outcome trees. When you align a result to a ToC outcome, the list of available outcomes comes from these services. PRMS does not author ToC content.

AWS Cognito and Active Directory

Identity and authentication. You log in with your organization credentials; Cognito and Active Directory verify who you are and pass that confirmation to PRMS. PRMS does not store your password or manage your account in the directory.

CGSpace

The CGIAR open-access repository. Knowledge product results in PRMS include a stable handle identifier sourced from CGSpace. This handle gives the knowledge product a permanent, citable reference that remains valid regardless of where the document is hosted.

MQAP

The Metadata and Quality Assessment Platform. For knowledge product results, PRMS can look up additional bibliographic and quality attributes via MQAP. This surfaces data such as open-access status and quality scores without requiring manual entry.

AWS S3 and SharePoint

Evidence file storage. When you attach a file to a result as supporting evidence — or when PRMS stores documents such as narratives and reports — those files land in AWS S3 or a SharePoint document library, depending on the document type. PRMS manages the links; the files themselves live in these external stores.

RabbitMQ

Asynchronous messaging for reporting metadata exports. When large reporting jobs are triggered — such as compiling reporting metadata across a phase — the work is queued in RabbitMQ so it can be processed in the background without blocking your session. You continue working while the export completes.

Pusher and WebSockets

Real-time notifications and live updates. When a result you are watching changes status, when a QA comment is added, or when a share request arrives, Pusher delivers the notification to your browser instantly — without you needing to refresh the page.

Hotjar and Microsoft Clarity

Client-side session analytics. These tools record aggregated, anonymized usage patterns — such as where users click and how they navigate forms — so the PRMS product team can identify usability issues and prioritize improvements. No result content or personally identifiable data is sent to these services.

What these integrations mean for your workflow

Most of these connections are invisible during normal use. You do not need to configure them or think about them while submitting results. They become relevant only when something is missing or behaving unexpectedly.
Catalog dropdowns are sourced from CLARISA. If an entry is missing, it is not in CLARISA — or has been deactivated there. Contact your CLARISA administrator to have the entry added. The change will appear in PRMS within the next sync window (within an hour for priority data, up to 8 hours for other catalogs).
ToC outcomes come from your Initiative’s external ToC service. If an outcome is absent, it may not yet be published in that system. Contact your Initiative’s ToC coordinator to have it added at the source.
Authentication is handled by Cognito and Active Directory. If you can log in to other CGIAR systems but not PRMS, your account may not have a PRMS role assigned. Contact your platform administrator.
Evidence files are stored in AWS S3 or SharePoint. If a file link is broken, it may indicate the file was deleted from the underlying storage, or that a link was saved incorrectly. Contact your platform administrator to investigate.
Real-time alerts depend on the Pusher connection. If you are behind a strict corporate firewall or proxy, the WebSocket connection may be blocked. In that case, notifications will appear the next time you load the page. Contact your IT team if the issue persists.

A note on ownership

PRMS integrates with these systems but does not own or operate any of them. Requesting changes to catalog data, user accounts, file retention policies, or identity configurations requires contacting the administrators of the relevant external system — not the PRMS platform team. When something in one of these systems changes (a center’s name is updated in CLARISA, a user is removed from Active Directory, a CGSpace handle is minted for a new publication), PRMS picks up the change through its regular sync and connection mechanisms. No manual intervention in PRMS is needed for most updates.

Build docs developers (and LLMs) love