Skip to content

Behavior Reference

The behavior layer is intentionally thin:

  • Controllers route — handle requests, redirect after submit, transform params.
  • Policies authorize — decide who can do what, which fields they can see, which records they can access.
  • Interactions act — encapsulate business logic for custom operations (publish, archive, import, send invitation).

Registering an action and rendering it lives in Resource › Definition and Resource › Actions. This section covers writing the controller hook, policy method, or interaction class behind it.

For multi-tenant relation_scope and entity scoping, see Tenancy › Entity scoping.

At a glance

ConcernWhere it lives
Field rendering (inputs, displays, columns, search/filters)Definition
Custom operations (publish, archive, import)Interaction + Action on the definition
Authorization rulesPolicy
Tenant scoping (relation_scope)Policy + Tenancy
Custom redirect logic, param munging, custom index query shapeController hook
Presentation of parent/entity fieldsController presentation hooks

Released under the MIT License.