Test a theme change safely | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/crm-theme-brand-style-manager-test Publisher: Pixie Technologies LLC Custom CSS, reset and operational control Test a theme change safely Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Follow this guide to use a controlled browser/session and verify admin, client, login and external-form pages. Audience: CRM administrators and authorised front-end implementers; Permission: Administrator; Module v2.3.0; Where to goAdmin Area → Setup → Theme Style Before you start - Verify the module is active and use the exact navigation shown above. - Use an account with the stated module and core CRM permissions. - Use known test records when changing statuses, visibility, saved filters or global navigation. What this guide helps you do Use a controlled browser/session and verify admin, client, login and external-form pages. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow. Follow these steps - Go to Admin Area → Setup → Theme Style. - Select the record or action required for test a theme change safely. - Complete the displayed fields and choices described in this guide. - Save, submit, approve or confirm the action as shown on screen. - Refresh the relevant list, record or report and verify the expected result. Fields and options WorkspaceAdmin Area → Setup → Theme Style ActionUse a controlled browser/session and verify admin, client, login and external-form pages. Rules and limits - Only controls rendered by the supplied module are documented; hidden AJAX helpers are mapped to their visible parent workflow. - Core CRM record permissions and module permissions are both enforced where the code checks them. Check it worked - The test a theme change safely action completes without a validation or permission error. - The affected record, stock balance, response, session or style reflects the saved state. - Audit, notification, report or portal evidence appears only where the module code creates it. Security, privacy and operational checks - Use a controlled test record before applying changes to live inventory, recipients, visitor tracking or global styling. - Grant only the minimum module and core CRM capabilities needed for the task. Related guides Clear custom CSS explicitly (https://pixiecrm.com/help-centre/crm-theme-brand-style-manager-clear-custom)Custom CSS, reset and operational control (https://pixiecrm.com/help-centre/topic/crm-theme-style-custom-css-reset)Browse all CRM Theme & Brand Style Manager guides (https://pixiecrm.com/help-centre/category/crm-theme-brand-style-manager)System customisation (https://pixiecrm.com/help-centre/category/system-customisation)Top navigation and header (https://pixiecrm.com/help-centre/use-the-top-navigation-and-second-header)Client portal (https://pixiecrm.com/help-centre/category/client-portal)Data, privacy and security (https://pixiecrm.com/help-centre/category/data-privacy-security)Advanced Task Filters (https://pixiecrm.com/help-centre/category/advanced-task-filters)Advanced Lead Filters (https://pixiecrm.com/help-centre/category/advanced-lead-filters)