> For the complete documentation index, see [llms.txt](https://userguide.zappost.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.zappost.com/zap-post-web-app/zap-post-user-guide/zap-app/using-the-zapp/settings/account-details.md).

# Account Details

The account details screen (found under 'Settings') in the ZAP-APP allows you to view and amend your company logo, details and address information. 

This information is used in various areas of the system which will be covered in this document. 

<figure><img src="/files/NXWmDIZqe26uAMT0poL6" alt=""><figcaption></figcaption></figure>

## Company Logo

This logo will be used in various UI's within the ZAP APP to show users which account they're on. \
This logo will also be exposed in the ZAP designer should you wish to include your logo in your ZAP Designs.&#x20;

<figure><img src="/files/45TMKSJNhZ5LAzEAVYP2" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Your uploaded logo should be a png or jpeg file with recommended dimensions 300px x 300px.
{% endhint %}

## Company Details

<figure><img src="/files/wbTtYdZNLoKO92yDUhPm" alt=""><figcaption></figcaption></figure>

Here you can edit your company name, phone number, accounts payable email and select your business sector. \
\
Company Name - Used for display and document composition purposes

Phone Number - Used for contact where necessary.&#x20;

Account Payable Contact Email - When this is populated the email address will be CC'd into any invoicing emails.&#x20;

Sector - This will dictate which sector templates show by default when selecting campaign templates and artwork.&#x20;

## Company address

<figure><img src="/files/kWqnWMWxtRQoVj1p58pT" alt=""><figcaption></figcaption></figure>

This is used for document composition and contact purposes so we can deliver and physical proofs when requested.&#x20;


---

# 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://userguide.zappost.com/zap-post-web-app/zap-post-user-guide/zap-app/using-the-zapp/settings/account-details.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.