Last updated
Resource model definitions use Capabilities to identify reusable behavior exposed through the public API. Capability names describe what API clients can use; they do not mirror PHP traits, interfaces, or other framework implementation details.
Each capability page defines the reusable resource behavior without maintaining an inventory of implementing resources. A resource's Model Definition links the capabilities it supports and describes the resource-specific fields, effects, and constraints. Shared request, resolution, and enforcement mechanisms remain in their dedicated Introduction sections.
Module Permissions are application-level prerequisites that determine whether the authenticated user's role can use a module or operation.
Targetables define the Users and Departments assigned to a resource. Depending on the resource, they represent participants, recipients, or responsible parties and may affect visibility.
Entity Permissions grant resource-specific permission keys to Users, Roles, or Departments. A resource can own these grants directly or inherit their effect through a parent resource.
A resource may combine these concepts. A module permission does not make a user a Targetable, and being targeted does not create an Entity Permission.
Last updated