> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/partner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.360dialog.com/partner/partner-hub/profile.md).
# Profile
This page describes how to manage and preview Partner branding
The Partner Profile section allows for the customisation of brand assets that are visible to clients during their onboarding journey. Maintaining an up-to-date profile ensures brand consistency and professional representation across the platform.
{% hint style="info" %}
**Partner Profile vs WhatsApp Business Profile**
Note this section is unrelated to the Business profile that appears to End-users in the WhatsApp App. \
[Learn more about WhatsApp Business Profiles here.](https://docs.360dialog.com/docs/resources/phone-numbers/business-profiles)
{% endhint %}
#### Accessing Profile Settings
To modify brand details, [open Partner hub](https://app.360dialog.com/), navigate to the settings:
### Brand Customisation
Partners can manage the following visual and textual elements to align the interface with their corporate identity:
* **Company Logo** - Upload or update the official company logo by clicking Change photo.
* **Brand Name** - Add or update the public-facing brand name by clicking the Pencil button. This name is displayed to clients.
---
# 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.360dialog.com/partner/partner-hub/profile.md?ask=&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.
