Field Monitoring
1.0.0
1.0.0
  • Field Monitoring Module Documentation
  • INTRODUCTION
    • Glossary / Terminology
    • FAQ
    • Report an Issue / Contact us
  • PRODUCT / END-USER DOCUMENTATION
    • Overview
      • User roles and permissions (?)
    • Field Monitoring Module Navigation
    • Overall User Interface
    • Settings section
      • Adding and Editing Questions
      • Sites Management
    • Plan section
      • Building the Rationale For the Monitoring Activity
      • Logging Known Issues
      • Prestructuring Field Monitoring Activities
    • Collect section
      • Activities Overview
      • Drafting a Monitoring Activity
      • Checklist / Questionnaire Setup
      • Checklist Review
      • Assigning / Accepting / Rejecting a Visit
      • Data Collection
      • Report Finalization
      • Submission / Completing a Monitoring Activity
    • Analyze section
      • Monitoring Activity
      • Country Overview
    • FMM workflow (?)
  • TECHNICAL DOCUMENTATION
    • Architecture
    • Development Setup
    • Deployment / DevOps
    • Data Model
    • Fixtures and Management Commands
    • Integration with permissions framework
    • API Documentation
      • Error Handling
    • Frontend
      • Module Structure
      • Build Process
Powered by GitBook
On this page
  1. TECHNICAL DOCUMENTATION

Integration with permissions framework

PreviousFixtures and Management CommandsNextAPI Documentation

Last updated 5 years ago

For Field Monitoring Module we use library which is also being used in partners/psea modules.

Everything related to permissions is located inside etools.applications.field_monitoring.planning.activity_validation package, which consists of:

  • validations (state related + stateless),

  • main validator class (ActivityValid)

  • main permissions class (ActivityPermission)

  • permissions matrix (permissions_matrix.csv)

__

etools-validator