Default Visibility

Omitting the Property

// No modeVisibilitySettings at all — visible in all five modes
{
  "id":   "first-name",
  "type": "text",
  "label": "First Name"
  // modeVisibilitySettings omitted → visible in edit, view, design, admin, preview
}

Omitting Individual Mode Flags

// Only 'preview' is false — all other modes default to true (visible)
{
  "id":   "email",
  "type": "email",
  "label": "Email Address",
  "modeVisibilitySettings": {
    "preview": false   // hidden in preview
    // edit, view, design, admin all default to true → visible
  }
}

Effective Visibility Table

The Opt-In-to-Hiding Philosophy

Defaults to visible is intentional. When you add a new control to a form, it works immediately in all modes without any extra configuration. You only need to configure modeVisibilitySettings when you want to deviate from universal visibility. This keeps simple forms simple.

parseSchema Normalisation

When parseSchema() processes a control, it fills in any missing mode flags with true — so the engine always works with a fully-specified object internally:

// Input schema (as authored):
{ "modeVisibilitySettings": { "preview": false } }

// After parseSchema() normalisation (internal representation):
{
  "modeVisibilitySettings": {
    "edit":    true,
    "view":    true,
    "design":  true,
    "admin":   true,
    "preview": false
  }
}

// Your code in a custom player can always safely read any mode flag:
const isVisibleInEdit = control.modeVisibilitySettings?.edit ?? true;
// → true (because parseSchema filled it in)