Per-organisation data fields
Custom fields
Customers & leads — Admin / Agent
Beagle CRM ships with a fixed set of customer and lead fields that cover most cases. Custom fields let your organisation capture extra information that matters to your process — account managers, industries, renewal dates, qualification scores, anything not in the built-in schema. Definitions are scoped to a single organisation, so other tenants never see your fields or values.
Where to find it
Open the organisation menu in the top-right of any
page and choose Custom Fields. The link is
visible to Admins and Agents. Direct URL: /orgs/<slug>/settings/custom-fields.
Who can do what
- Admin — create, edit, archive, hard-delete, fill in values.
- Agent — create, edit, archive, fill in values. No hard-delete.
- Viewer — read-only on values.
Creating a field
Click + New custom field. Fill in:
- Label — what humans see (e.g. Account Manager).
- Field key — auto-generated from the label. Used in the import template column header. Editable until first save, then locked.
- Description — optional help text shown next to the field on forms.
- Field type — pick once, cannot be changed afterwards. Choose carefully.
- Options — only for Single select / Multi select. Add value/label pairs.
- Visibility — toggle whether the field appears on the add form, the detail page, the customer list (as a column), and whether it is active.
- Behaviour — Required on create blocks save when empty. Important highlights the field amber on the detail page when empty (without blocking).
Available field types
- Text — single-line string
- Long text — multi-line string
- Number — decimal number
- Money — decimal with 2 dp
- Date — ISO date
- Yes / No — boolean
- Single select — one value from a list
- Multi select — many values from a list
- URL — validated URL
- Email — validated email
- Phone — phone number
Filling in values
On the customer form, switch to the Custom Fields tab (only shown when at least one field exists for customers). On a lead, scroll to the Custom Fields section near the bottom of the form. Save persists the values transactionally with the parent record — if a value fails validation, the whole save rolls back.
Detail pages
Customer and lead detail pages show an Additional Information panel with the configured custom values. Empty Important fields render with an amber label as a soft prompt to fill them.
Customer list columns
Tick Available as list column on a definition to surface the field in the customer grid. Each column gets a built-in filter typed for the field (text, number, date) and you can pick the same filters as for built-in columns.
Imports
The customer import template includes one column per active
customer custom field, prefixed CF: <Label>. Re-download the template after creating new
fields. Bad values surface as per-row errors so the rest of the
import keeps running.
Archive vs delete
Archive hides the field everywhere but keeps stored values in case you need them. Delete (admin only) permanently removes the field and every value attached to it; the confirmation prompt warns you. Use the Stats button first to see how many records hold a value.
GDPR / anonymisation
When an admin anonymises a customer, all custom field values for that customer are cleared in the same transaction as the built-in personal fields. Field definitions are unaffected; other customers’ values remain.
Things to know before you start
- Field type is permanent. If you pick the wrong type, archive the field and create a new one with the right type.
- Field key is locked after first save. It is used in import templates — pick something stable.
- Removing a select option that is already in use will cause the next save of those records to fail validation. Clear or migrate the values first.
- Required on create only fires when the field is also visible on the add form.
- Lead custom fields are not yet surfaced as columns on the lead grid — on the roadmap.