Appearance
Custom Fields
Defining fields
Custom field creation and editing is limited to superusers. These can be created per agency account on request by the Syngency team. Ideally they should be used sparingly where existing fields or workarounds are unsuitable.
Field settings
| Setting | Description |
|---|---|
| Name | Display label shown in the UI |
| Handle | Slug used to access the field in templates, e.g. manager_email |
| Type | See Field types |
| Help Text | Optional hint displayed below the field in the UI |
| Placeholder | Optional placeholder text shown inside the input |
| Sections | One or more defined sections the field belongs to. A section relates to a specific element. Section names are shown in the UI, and section handles are used in the custom field template path, e.g. profile_links |
| Sort Order | Controls the display order of the field within its section |
| Required | Marks the field as required in the UI |
| Searchable | When assigned to a Booking, the field is available as a search filter |
Field types
| Type | Description |
|---|---|
Contact | A selectable contact from the agency's configured Contacts |
Date | A single date |
DateRange | A start and end date |
File | A file attachment |
Image | An image upload |
Number | A numeric value |
RichText | HTML rich text content |
Select | A single value from a defined list of options |
Tags | Multiple values from the agency's configured tags |
Text | A short plain text string |
Textarea | A multiline plain text block |
Time | A time value |
URL | A URL string |
Supported elements
Custom fields can be attached to the following objects:
| Element | Note |
|---|---|
Booking | Each defined Section appears at the bottom of the left menu |
Talent | Each defined Section appears at the bottom of the left menu |
Contact | Each defined Section appears at the bottom of the left menu |
Page | Each defined Section is rendered as a tab in the page editor panel |
Post | Each defined Section is rendered as a tab in the post editor panel |
Template usage
From a corresponding template and object (e.g. a model or page), access custom field values using the section handle and field handle defined in the field settings.
liquid
{{ [object].custom_fields.[field_section_handle].[field_handle].value }}
{{ model.custom_fields.profile_links.manager_email.value }}
{{ page.custom_fields.page_options.hero_image.value }}Submission forms
Talent custom fields can be filled via a submission form. Use the section handle and field handle as the input name in the format custom_fields[section_handle][field_handle]. For Select fields, the available options are exposed via .config.select_options.
Examples
Select field with configured options:
liquid
<label for="english_language_ability">How is your English language?</label>
{% select id:'english_language_ability', name:'custom_fields[act_information][english_language_ability]', options: custom_fields.act_information.english_language_ability.config.select_options, blank_option: true %}Plain input:
liquid
<label for="number_in_group">Number of people in your act</label>
{% input type:'text', id:'number_in_group', name:'custom_fields[act_information][number_in_group]' %}