> For the complete documentation index, see [llms.txt](https://docs.atomyx.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.atomyx.io/atomyx-submit/troubleshooting/atomyx-submit-troubleshooting/branding-issues.md). # Branding Issues Branding issues affect how the Atomyx Submit portal appears to customers. The most common problems involve the configured logo or primary colour not appearing as expected. ### Logo not appearing #### Typical symptoms * the logo is missing or broken * it appears for some users but not others * it was uploaded in the configuration but does not show in the live portal #### What to check * file size * supported file format * whether the configuration was actually saved * whether the browser is showing a cached version #### How to resolve it * optimise the logo file size * use a supported format such as PNG, SVG, or JPEG * save and reopen the configuration to confirm the asset is stored correctly * clear browser cache and do a hard refresh ### Primary colour not applied #### Typical symptoms * the portal still shows the default colour * the configured colour appears in settings but not in the live experience * old and new sessions may show different behaviour #### What to check * colour format * whether the configuration was saved * whether existing sessions are caching earlier settings #### How to resolve it * use a hex colour value * resave the configuration and refresh the portal * test with a new submission session * clear browser cache if the portal appears to be using an older visual state ### Practical guidance Keep branding simple and deliberate. In Atomyx Submit, branding should strengthen trust and recognisability without making the portal harder to use or maintain. ### Related pages * **Branding and Language** * **Portal Setup** * **Submit Troubleshooting** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.atomyx.io/atomyx-submit/troubleshooting/atomyx-submit-troubleshooting/branding-issues.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.