PRP
  • PRP Documentation
  • Introduction
    • Glossary / Terminology
    • Indicators
      • Disaggregations
      • Calculating progress
    • FAQ
    • Releases / Changelog*
    • Report an Issue / Contact us
  • Product / End-user Documentation
    • IP Reporting
      • Overview
      • Partner roles and permissions
      • User Interface
      • Setting calculation methods for indicators
      • Progress Reports
        • Reporting Overview
        • Special Reports (SR)
        • Humanitarian Reports (HR)
        • Quarterly Progress Reports (QPR)
        • Reporting Process
        • Data Uploader for QPR and HR
      • Various data exports
    • Cluster Reporting
      • Overview
      • User Authentication, Roles and permissions
      • AD Integration
      • Response Plans
      • Cluster Indicators
      • Response Plan Dashboard
      • Response Parameters setup
      • Planning your action as a Partner
      • Reporting on results
        • Reporting to UNICEF
      • Analysis of results
      • OCHA Integration
    • ID Management
      • Overview
      • AD Integration & Sign In
      • Email Notifications
      • User Statuses
      • Permissions
      • IP ID Management
        • User Interface
        • Users screen
      • Cluster ID Management
        • User Interface
        • Users screen
        • Partners screen
  • Technical Documentation
    • Architecture
    • Development Setup
    • Deployment / DevOps
    • Data Model
    • API Documentation
      • Error Handling
    • CartoDB location sync
    • OCHA Integration - Research Summary
      • Response Plan Import
      • Project Import
    • ID Management
      • Backend API's
    • Handover session question
Powered by GitBook
On this page
  1. Product / End-user Documentation
  2. Cluster Reporting

Response Plans

PreviousAD IntegrationNextCluster Indicators

Last updated 6 years ago

Selecting a Response Plan

In the context of the workspace the user has selected, they will have to always select a response plan, before they can proceed further. This ensures that the entire user interface is functioning and showing data for one response plan at a time only, and keeps reporting / data / setup for response plans not to overlap or interfere with each other.

Partner should only see response plans for clusters they belong too (#)

They can select many Clusters or at least one for this response plan. There is no "edit response plan" capability. It can be done as an admin fix in django admin.

If the response plan the IMO would like to work on, is not there, they can add a new response plan or select an existing one from OCHA Response Planning & Monitoring (RPM). See for more details.

For Custom Response Plans, IMO can fill out Response Plan name, plan type, start date, end date, and select cluster(s) involved. Plan types include HRP, FA, and Other (#)

OCHA integration
910
678