> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/admin/branding/branding.md).

# Branding

The Branding section in the Admin Portal lets you customize the visual identity applied across your Welkin environment — including your organization's logo and the font used in generated documents.

***

## Logo

Upload your organization's logo to display it across the platform.

### Upload a logo

1. In the Admin Portal, navigate to **Branding**.
2. In the **Logo** card, click the file picker to select an image from your device.
   * Accepted formats: **PNG**, **JPEG/JPG**
   * Maximum: 1 file
3. A preview of the selected image appears above the file picker.
4. Click **Upload** to save the logo.

### Delete the current logo

1. In the **Logo** card, click **Delete**.
2. The logo is removed immediately and the placeholder is restored.

***

## Font Family

Choose the font that is used across all generated document templates (for example, PDF exports from assessments and forms).

### Available fonts

| Font                 | Notes   |
| -------------------- | ------- |
| **Noto Sans**        | Default |
| **Liberation Serif** |         |
| **Source Serif 4**   |         |
| **Inter**            |         |
| **IBM Plex Sans**    |         |

### Change the font

1. In the Admin Portal, navigate to **Branding**.
2. In the **Font Family** card, click the radio button next to the font you want to use.
   * Each option shows a sample text preview in that font.
3. The selection is saved automatically — no additional Save button is needed.

The updated font applies to all newly generated documents. Previously generated documents are not affected.

***

## Related Topics

* [Admin Portal Overview](/admin/admin.md)
* [Environments](/admin/environments/environments.md)


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.welkinhealth.com/admin/branding/branding.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.