Fields define the data points that can be collected and processed in forms for leads and users or feeds. To keep structures consistent and reduce repetitive work, there are three levels of fields available:
- Custom fields – fields created directly inside a structure, dedicated only to that structure.
- Local fields – fields created in the workspace settings that can be reused across multiple structures.
- Global fields – system fields predefined by PalDock and mapped to key features such as user details and integration field mapping. Can be reused across multiple structures.
We recommend using global fields whenever possible. If a required field is missing, use local or custom fields as needed.
Global Fields
Global fields are system-wide fields predefined across all PalDock workspaces. They simplify integrations both between PalDock workspaces and with external systems, because when global fields are used, there is no need to manually map them.
They are intended for values that repeat very often and should remain consistent everywhere, such as First Name, Last Name, Email, Phone, and many others.
- Some global fields are linked to the user’s multi-workspace account. When a user updates their value (e.g. changes their name), the update is reflected across all workspaces they have access to.
- These fields cannot be edited or customized by an Admin. They can only be updated by the user themselves.
- To customize a global field, you need to create a Local field instead. However, a local field is not linked to the multi-tenant account.
- Global fields use a dedicated prefix (e.g. g_) that cannot be reused for anything else.
👉 We recommend using global fields whenever possible, since all library-based integrations already rely on them. This saves you and your partners significant time during setup and maintenance.
Local Fields
Local fields are similar to global fields but are defined at the workspace level by the admin. They allow you to create workspace-wide fields that can be reused across multiple structures, without the need to redefine them for every form.
- Local fields can be fully edited and customized.
- They are useful when a suitable global field is missing.
- Once created, local fields appear in a dedicated list and can be easily reused in any structure.
- When a local field is used inside a structure, the system automatically applies the correct prefix and disables manual editing of the field name to ensure consistency.
Custom Fields
Custom fields are fields defined directly within a single structure (e.g. a specific lead form).
- They exist only in that one structure.
- They are fully customizable by the user creating the form.
- They are best used when a field is unique to a specific form or use case and doesn’t need to be reused elsewhere.
Creating Fields
Custom and Local fields can be created in two ways:
- Custom field creation – create a field directly inside a Lead Structure by clicking Add. The new field will appear in the structure immediately, and will be preselected if no other field is chosen.
- Local field creation – go to the Local Fields section in Settings, click Add, and create a new local field. To use it in a specific structure, open that structure and instead of adding a new field, click the selection icon (dashed square) next to the field name and choose a predefined field from the list. Once selected, the field is visually marked as a local field, including any modifications applied (e.g. via Modify Field), which is indicated by an icon.