Customise theme and interface styling
Apply supported visual settings and reset them without editing core application files.
Feature pathSetup → Theme Style
Before you beginThe 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 this feature does
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.
Step-by-step workflow
- Open Setup → Theme Style using an administrator or appropriately permitted account.
- Review 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.
Important fields and decisions
Setting nameConfirm this information is accurate and appropriate for the record.
Enabled statusConfirm this information is accurate and appropriate for the record.
Scope or audienceConfirm this information is accurate and appropriate for the record.
Order or positionConfirm this information is accurate and appropriate for the record.
Display labelConfirm this information is accurate and appropriate for the record.
Reset or fallback behaviourConfirm this information is accurate and appropriate for the record.
Checks before completion
- 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
Related guides
Was this guide helpful?