Modules & Actions

Full RBAC model with module-level permission matrices.

The Full authorization model organizes permissions into modules — discrete functional areas of your application — with actions assigned per module per role.

How modules work

A module represents a bounded area of your app (e.g., BOOKINGS, PROPERTIES, INVOICES). Each module defines the actions that are meaningful within it. Roles are then granted specific actions on specific modules.

Role: Property Manager
├── PROPERTIES → [READ, CREATE, UPDATE, DELETE]
├── BOOKINGS   → [READ, LIST]
└── INVOICES   → [READ]

Registering modules

Modules are registered by your application via the API. Registration is durable — processed via background jobs to ensure consistency.

curl -X POST https://api.platformxe.com/api/v1/permissions/modules \
  -H "Content-Type: application/json" \
  -H "x-api-key: pxk_live_your_api_key_here" \
  -d '{
    "name": "BOOKINGS",
    "description": "Booking management",
    "actions": ["READ", "CREATE", "UPDATE", "DELETE", "LIST", "APPROVE"]
  }'

await px.permissions.registerModule({
  name: 'BOOKINGS',
  description: 'Booking management',
  actions: ['READ', 'CREATE', 'UPDATE', 'DELETE', 'LIST', 'APPROVE'],
});

Module limits by plan

Plan	Max modules
Free	5
Basic	20
Pro	50
Enterprise	Unlimited

Assigning module permissions to a role

curl -X PUT https://api.platformxe.com/api/v1/permissions/roles/role_abc123/modules \
  -H "Content-Type: application/json" \
  -H "x-api-key: pxk_live_your_api_key_here" \
  -d '{
    "modules": [
      { "moduleId": "mod_bookings", "actions": ["READ", "CREATE", "UPDATE"] },
      { "moduleId": "mod_properties", "actions": ["READ", "LIST"] }
    ]
  }'

await px.permissions.setModulePermissions('role_abc123', {
  modules: [
    { moduleId: 'mod_bookings', actions: ['READ', 'CREATE', 'UPDATE'] },
    { moduleId: 'mod_properties', actions: ['READ', 'LIST'] },
  ],
});

Federated keys

When modules are shared across apps via Federation, they use a prefixed key format: PREFIX:MODULE. For example, if an app with prefix LT registers a BOOKINGS module, it becomes LT:BOOKINGS in the federation namespace.