How-to guide

Configure company logos and favicon

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Upload production-ready brand assets and verify light and dark interface contexts.

Audience: AdministratorFeature: SettingPermission-aware

Plain textJump to steps

Learn with Pixie CRM

Watch this workflow

Follow real application screens at your own pace, with English captions and a matching written guide.

All video tutorials

1:35 English captions

Upload and verify your company logo

Upload a company logo in Pixie CRM with live clicks. Open General settings, choose the image file, save the settings and confirm the logo appears in the workspace header and preview.

Chapters & transcript Watch on YouTube

Recorded in a demonstration workspace; available options depend on your plan and permissions.
Visit the Pixie CRM YouTube channel

Where to goSetup → Settings → Company Information / Branding

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 this guide helps you do

Upload production-ready brand assets and verify light and dark interface contexts. Pixie 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 → Settings → Company Information / Branding 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 Pixie 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.

Settings to check

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:payment check report approval client portal notifications email customers custom fields

Was this guide useful?Your response is stored only in this browser.