Skip to content

Classifications overview

Classifications describe conditions about rows in a table.

They answer questions like:

  • Is this booking confirmed?
  • Is this customer active?
  • Does this employee have an assigned manager?
  • Is this room available for booking?

Each classification evaluates to either true or false for every row.

Other parts of the system then use this result to decide what should happen.

For example, a classification might be used to:

  • hide rows from certain users
  • block invalid edits
  • filter lists
  • trigger notifications
  • decide whether something can be scheduled

What a classification is

A classification is a named condition attached to a table.

For each row, the system checks whether that condition is true or false.

Example:

Table: Person

Classification: Has email address

Condition:

email IS NOT EMPTY

Result:

Person Email Has email address
Anna anna@example.com true
Erik (empty) false

The classification does not change the data.
It simply describes something about the row.

Automatic evaluation

Classifications are evaluated automatically by the system.

Whenever data changes, the result of the classification updates automatically.

The same classification definition is used everywhere:

  • in the user interface
  • in API requests
  • in rules and permissions
  • in notifications
  • in scheduling

This ensures the system behaves consistently.

Types of classifications

Minyu supports three types of classifications.

Value classifications

Value classifications check a single column.

Example:

booking_status = "confirmed"

This classification could be named Confirmed booking.

These are often used for:

  • validation rules
  • filtering lists
  • simple conditions

→ Read about value classications

→ Read about predicates

Relational classifications

Relational classifications depend on related rows.

Example:

A booking might be considered valid only if the assigned room exists and is active.

This requires checking data in another table.

Relational classifications follow relations between tables to evaluate such conditions.

→ Read about relational classications

Logical classifications

Logical classifications combine other classifications.

Example:

Active customer AND Has valid contract

Logical classifications allow complex rules to be built from simpler ones.

→ Read about logical classications

Where classifications are used

Classifications influence many parts of the system.

They are commonly used for:

  • read rules (who can see a row)
  • write rules (whether changes are allowed)
  • filters in lists and searches
  • scheduling logic
  • notification triggers
  • integration logic

Because classifications are reusable, the same definition can affect multiple parts of the system at once.

A useful way to think about classifications

A simple way to think about classifications is:

A classification is a named condition about a row that the rest of the system can use.

Instead of repeating the same logic in many places, the system defines it once and reuses it everywhere.

Related concepts