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

# Customize your public page

Customize your public page to fit your brand. Add your logo, change colors, and button style. This page will be exposed to your audience when you share a public link.

(e.g. customize buttons' colors to fit your logo colors)

### Brand logo&#x20;

Add your own logo to customize your public page.&#x20;

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/1pz22xivp8>" %}

* Toggle on "Brand logo" to customize the top-left logo of your guideflow's public links.
* Click on "Upload a new picture" to upload your logo.
* Select your picture.&#x20;

### Customize your public page call-to-actions

Edit button titles and colors to customize your public page.&#x20;

* Toggle on "Custom Call-to-action" to customize the top-right buttons of your guideflow's public links.
* Edit the primary button's title.
* Add an URL to your primary button.
* If you want, customize the button's color and add a gradient.
* Edit the secondary button's title&#x20;
* Add an URL to your secondary button.
* If you want, customize the second button's color and add a gradient.

{% hint style="info" %}
You can delete the secondary button if not needed&#x20;
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.guideflow.com/help/branding/customize-your-public-page.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
