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

# Customizations

This guide walks you through personalizing your workspace with your company’s branding, primary color, and terms & conditions messaging.

### 1. 🔧 Customizing Branding

#### 🖼 Company Logo

You can upload your organization's logo to reflect your brand throughout the FenixPyre experience.

* **Recommended Size**: `100×100px`
* **Supported Formats**: `PNG`, `JPG`

**How to Update the Logo:**

1. Click the **Choose File**
2. Upload your desired logo image.
3. To remove the logo, click **Remove**.

#### 🎨 Brand Color

Customize the accent color used throughout the FenixPyre platform (e.g., buttons, links, highlights).

You can:

* Select from preset colors (shown as circles).
* Or enter a **custom hex code** (e.g., `#22c55e` for green).

💡 **Live Preview**: As you change the color, you will see a real-time preview on the right panel showing how it appears in the interface.

***

### 2. 📄 Customize User-Facing Terms & Conditions

Use this section to define the legal message shown to users when they download encrypted or unencrypted files.

#### ✏️ Editable Fields

* **Heading**: The title of your agreement (e.g., *Access Authorization Terms & Conditions*).
* **Message Body**: Use rich text formatting to describe your terms.

Supported formatting includes:

* Bullet points
* Bold, Italics, Underline
* Alignment options

#### 🧪 Live Preview

To the right, a **live modal preview** shows how the message will appear to your users before they download files.

#### Example Message

```
- This download may contain confidential and privileged information.
- If you are not the intended recipient, please notify the sender immediately and delete this download and destroy any copies.
- Any dissemination or use of this information by a person other than the intended recipient is unauthorized and may be illegal.
```

***

### ✅ Best Practices

* Always use your **official logo** to instill brand trust.
* Choose a **color** that aligns with your corporate theme.
* Ensure your **terms and conditions** comply with legal and compliance requirements.
* Review the **live previews** to confirm everything looks perfect before saving.

Let your brand shine confidently across the FenixPyre platform! ✨


---

# 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.fenixpyre.com/fenixpyre-for-admins/admin-dashboard/customizations.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.
