Skip to content

Permissions Module

Overview

The Permissions module manages system permission records used by RBAC enforcement.

API Prefix: /api/v1/permissions

Route Verification Status

  • Source Router: app/api/v1/endpoints/permissions.py
  • Live Route Count: 2
  • Verification State: Verified (2026-06-28)
  • Canonical Tracking: docs/API_ROUTE_DOCUMENTATION_TODO.md
  • Verification Method: Route decorators extracted from @r.<method>(...) in app/api/v1/endpoints/permissions.py.

API Endpoints (Verified Against Live Router)

GET  /api/v1/permissions
POST /api/v1/permissions

For method/path/source-line details, see: - docs/API_ROUTE_LIVE_REFERENCE.md -> section permissions.py (2 routes)

Authorization Notes

  • GET /api/v1/permissions requires fetch_permission.
  • POST /api/v1/permissions requires create_permission and active superuser access.

Data Model (High Level)

  • Permission entity includes permission identity and metadata used by role/action mapping.
  • Integrated with role and user access enforcement across modules.