> 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/implementation/portal-configuration/branding-and-language.md).

# Branding and Language

The goal is to allow portal deployments to reflect the provider's identity while keeping the user experience consistent and reliable.

### Visual branding

The main visual elements that can be configured are:

* **logo**
* **primary colour**

The logo can appear in the portal header and on generated proof pages.

The primary colour is typically used for buttons, links, progress states, and other key interface accents.

### Content customisation

In addition to visual identity, customer-facing text can also be tailored.

Typical customisable areas include:

* welcome messages
* upload instructions
* customer-facing error messages
* proof page text and disclaimers
* approval and notification emails

### Language support

If the portal serves international customers, language should be designed in from the start.

Language configuration may affect:

* portal labels and buttons
* customer instructions
* preflight issue descriptions
* proof page labels and metadata
* email notification templates

### Practical advice

Plan language and branding early.

Retrofitting:

* multiple languages
* white-label variants
* product-family branding differences

is usually much more expensive later than including them in the original portal design.

### Best practice

Keep the portal clean and understandable first.

Branding should support trust and clarity, not overwhelm the submission workflow.

### Next steps

* Go to **API Integration**
* Go to **Submit Troubleshooting** if branding changes are not appearing correctly


---

# 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/implementation/portal-configuration/branding-and-language.md?ask=<question>
```

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.