Give a Helpdesk an accessible brand treatment, useful links, and an accurate support destination This guide keeps the work focused on Helpdesk appearance and navigation and provides a repeatable path that a new Humind user can follow without changing unrelated configuration.

A Humind Helpdesk is a published projection of eligible public Knowledge. It has its own address, content selection, languages, appearance, navigation, support destination, metadata, and immutable publication versions. Editing the configuration or Knowledge does not change the public site until a new coherent version is published.

Before you begin

Access: Helpdesk and company settings write permissions are required. Brand assets must be approved for public use.

• Collect approved light and dark logos, favicon, colors, and alternative text.
• List required header links and one support destination.
• Decide which values should inherit from the Agent.

Work in the smallest owning area described below and keep the current customer-facing state available while you prepare the change. Before clicking any final action, confirm the active company, Agent, store, language, and market shown in Humind. A missing control can indicate read-only access or a capability that is not configured for this company. In that case, record the intended task and ask an administrator to review the exact permission or dependency. Do not bypass the boundary by sharing an account, copying data into another area, or promising a capability that the workspace does not expose.

Step-by-step workflow

1. Confirm the scope and current state

   Open Appearance and review inherited Agent values before creating Helpdesk-specific overrides.

   • Confirm the active company and Agent before editing.
   • Record the current state so the result can be compared after the change.
   • Stop if the screen or permission does not match the intended task.

2. Prepare the change

   Set readable colors, logo alternatives, and supported image assets, then inspect both light and dark previews.

   • Use the smallest change that completes the customer task.
   • Keep authoritative information in its owning source.
   • Review labels, dates, language, and customer-visible wording before saving.

3. Save and allow required processing to finish

   Open Links and assistance, add only maintained header links and an accurate primary action, and choose no contact, email, or external support link as appropriate.

   • Wait for the interface to confirm that the change is saved.
   • If synchronization, indexing, or publication is required, wait for its final state.
   • Reload the area and confirm the saved values persist.

4. Test the complete customer journey

   Save each section, test header, footer, navigation, contact action, mobile layout, and keyboard access before publication.

   • Use a fresh session and a realistic customer scenario.
   • Check desktop and mobile when the result appears on a storefront.
   • Capture the exact failing step if the outcome differs from the expectation.

Important limits and operating notes

• A successful save confirms persistence, not every downstream synchronization or public update.
• Workspace permissions can hide an area or allow reading without allowing changes.
• Do not copy volatile catalog, account, or customer facts into narrative content as a workaround.
• Test only supported capabilities that are visible and configured for the current company.
• Keep changes in Helpdesk appearance and navigation separate from unrelated Agent, Knowledge, catalog, Inbox, or Helpdesk work.

Verify the result

• Branding remains legible in light and dark themes.
• Every public link resolves to the intended safe destination.
• The support option matches staffed capability.
• The candidate works on desktop, mobile, and keyboard navigation.

Keep a short record of what you tested, which customer scenario you used, and what changed. This makes later troubleshooting more precise and helps another teammate reproduce the result without relying on memory.

Troubleshooting

An uploaded visual is not shown

Confirm the upload completed for the correct asset kind and center. Review inheritance versus override state, then reload the Helpdesk candidate.

A link or support action is invalid

Use a complete safe URL or supported internal path and provide every required label. Save the navigation section before publishing.

Related guides

• create a helpdesk and choose its address
• configure helpdesk languages and translations
• publish republish and unpublish a helpdesk
• troubleshoot changes that do not appear in the helpdesk