Customise theme and interface styling
Apply supported visual settings and reset them without editing core application files. 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 → Theme Style
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
Apply supported visual settings and reset them without editing core application files. 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 → Theme Style using an administrator or appropriately permitted account.
- Check the current value and understand which users, records or automated processes it affects.
- Enter or select the new configuration values. Keep labels concise and use the approved business terminology.
- Where credentials, email, webhooks or cron are involved, begin with a test or sandbox configuration.
- Save the change and confirm that Britixo CRM reports success.
- Test the affected workflow with a non-critical record and with a restricted user where permissions are relevant.
- Document the operational change and use the available reset or rollback option if the result is not correct.
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.
Browse connected topics:paymentcheckreportapprovalclient portalnotificationsemailcustomersdashboard widgetscustom fields
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.