Create custom fields
Follow this guide to add structured fields to supported record types and choose visibility and validation behaviour. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goSetup → Custom Fields
Before you startThe screen or action may be hidden when your role lacks permission, the related module is inactive, or a required setting has not been configured. Ask an administrator to review access rather than using another person’s account.
What you’ll accomplish
Add structured fields to supported record types and choose visibility and validation behaviour. Britixo CRM keeps the result connected to the relevant customer, staff member and operational history where the feature supports those relationships. That connection is important for search, reporting, client portal visibility and future automation.
Follow these steps
- Go to Setup → Custom Fields and select the new or add action.
- Select the correct related customer, contact, project or other parent record where the form requests one.
- Complete the required identity, ownership and date fields for the setting.
- Add financial, status, visibility or permission information that applies to the workflow.
- Add clear notes, content, line items or attachments so another authorised user can understand the record.
- Check validation messages and client-visible information, then save.
- Go to the saved record, confirm the status and activity entry, and perform the next workflow action only after review.
Fields and decisions to review
Setting nameCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Enabled statusCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Scope or audienceCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Order or positionCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Display labelCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Reset or fallback behaviourCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Checks before you finish
- Change only one area at a time.
- Record the previous value.
- Verify desktop and mobile behaviour after saving.
- Check whether the result should be visible to a customer contact or only to staff.
- Confirm the final status, activity entry, generated document or notification before leaving the record.
Permission and data safetyDeletion, refunds, signature clearing, module changes, payment configuration and privacy actions can affect linked records or legal history. Use the least destructive action available and follow your organisation’s approval process.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.