Skip to content

States and rules

A collection’s rules control which changes are valid:

  • States: a list field with allowed transitions (Draft → Sent → Accepted). Changing to a state without a transition is rejected.
  • Validations: conditions a record must meet to be saved, with their message.
  • Seal records (Sellar registros): from a given state on, the record can no longer be edited.
  1. Go to Settings → Collections → the collection → Rules (Reglas).
  2. Turn on States: choose the state field, the initial state and add transitions (from, to and which roles may use each one).
  3. A transition can ask for fields in a dialog (for example, the reason for losing a deal) and run code after the transition.
  4. Add validations with the message the person sees when they fail.
  5. Turn on Seal records and choose the state that seals.
  6. In the record page, transitions appear as buttons and in the stage bar.
  • Rules apply the same in the app, the API, MCP, scripts and automations.
  • Configuration collections only have validations.
  • A sealed record cannot be edited or versioned.
  • Only an administrator can force a state without a transition (to fix a mistake); the transition’s automations do not run.
  • States, transitions and validations are changed in the schema with patch_schema_draft (update_collection); format in get_field_guide and export_schema.
  • update_record changes the state only through a valid transition.
  • force_record_state: administrators only; moves the record to any state.