How to Configure Field Display in the Client Card?

Two entry points to the same visibility settings: (1) Client Fields — field definitions and visibility together, one header Save; (2) this menu item Field editor in the Client Card (/settings-page/op-settings/client-fields) — visibility block only; save with the op-settings header Save. The op-settings page includes a link back to Client Fields when you need to edit the field schema.

Configuring field display lets you choose which fields to show to operators in the client card and in the clients table. Custom fields must already be defined to appear in the list.

When You'll Need This

  • You need to hide or show standard fields (phone, name, client type, etc.).
  • You need to show custom fields created in Client Fields.
  • You need to change the display order of fields in the client card.

What's Important to Know

  • You can change visibility on Client Fields (best when editing fields and visibility together). Use this page when you only adjust visibility or prefer the op-settings menu. Custom fields must already exist in the configuration.
  • Standard fields — native OpClients columns: phone, bot_id, bot_name, fullName (from full_name). They can only be shown or hidden. Fields clientType, whiteLabel in the example may be custom fields in extra_data or legacy keys.
  • JSON format — each key = field name, value true = show, false = hide. Key order determines display order.

Before You Start

  • You are logged in with administrator or supervisor rights.
  • You have permission to save operator panel settings (canSave for the settings section).
  • For custom fields: they are already added in Client Fields (or you only adjust standard fields).

Step-by-Step Instructions

1. Open Client Card Field Editor

  1. Go to the Settings module through the menu or at /settings-page.
  2. In the side menu, find the "Settings" section (operator panel) and expand it.
  3. Click on "Field editor in the Client Card" (/settings-page/op-settings/client-fields).

2. Understand the JSON Format

The configuration is a JSON object. Key = field name, value = show (true) or hide (false):

{
  "phone": true,
  "bot_id": true,
  "bot_name": true,
  "fullName": true
}

Native OpClients fields (available without creation):

  • phone — phone number
  • bot_id — bot ID
  • bot_name — bot name (from join)
  • fullName — full name (column full_name)

Note: The page example may show clientType, whiteLabel — these are custom fields in extra_data or legacy keys. Create them in Client Fields if you use them.

Custom fields — add keys of fields created in Client Fields with value true to show.

3. Configure Display

  1. Use the toggles and/or visibility JSON (same block as on Client Fields).
  2. Click Save in the operator panel settings header (persists op-settings including client_card_fields).

4. Using Nested Objects (extra_data)

For individual custom fields from extra_data, you can use a nested object with the extra_data_flag flag. See the hint on the page for details.

What Happens Next

  • Settings are saved in client_card_fields (OpSettings).
  • Operators see only the selected fields in the client card and in the clients table.
  • Field order matches the key order in the JSON.

How to Verify Everything Worked

  • Open a client card in the operator panel and verify that only the selected fields are displayed.
  • Check the clients table in the Broadcast module.

Important Notes

  • ⚠️ Custom fields: define them in Client Fields first if not already done on your instance.
  • 💡 JSON must be valid: check syntax (commas, brackets).
  • 💡 If JSON is empty or invalid, the default display is used.