> For the complete documentation index, see [llms.txt](https://track360.gitbook.io/track360/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://track360.gitbook.io/track360/section-5-settings/editor/5.1-brand-management.md).

# 5.1 Brand Management

### Platform Default Settings

* Navigate by the **left Sidebar Menu** and click on **Brands**
* Navigate into the **Settings** section to configure all general user-related settings default:
  * **No Commission Deal**, to set a specific default deal or leave it empty
  * **Start Date of Affiliate Reports**, by default. Is useful to select “Since ever” option, the date will be set from the first available data.Anyway, the report range date could still be changed by filters of each report
  * **Block Traffic from**, set countries to block the traffic.
  * **Default Affiliate Support Email**, set a designated email to automatically send settings emails. *This email will appear in the affiliate page for them to contact the brand*
  * **Unassigned Employee Business Unit**, the default BU to assign when a new employee is not specified with one.
  * **Retired Employee Business Unit**, which Business Unit decides to move the employee after the inactivation.
  * **Affiliate Payments Require Management Approval**, set as default if a management approval is required or not for affiliate/IBs payments. This adds the extra step in the system "Payment final approval" the platform have for default, risk approval, marketing approval and execution

<figure><img src="https://4110691288-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1iHXZgeTSXZwHDnWa5S8%2Fuploads%2Ft5BjsrrJxySAHbZKlXY7%2Fimage.png?alt=media&amp;token=25b11de3-dea4-4d0d-9d81-bbdbed49e0f4" alt=""><figcaption></figcaption></figure>

### Affiliate Default Settings

* Navigate into the **Affiliate Configuration** section to set:
  * **Default Deal**, usually set to "No commission" by default, meaning affiliates won't have a deal until you assign one. Otherwise you can set a specific deal as default.
  * **New Affiliates Default Affiliate Manager**, select the manager who automatically assigned to affiliates upon registration or creation.
  * **New Affiliates Default Business Unit**, assigns new affiliates to a specific business unit by default.
  * **Email must be verified in order to login?**, select as default if it is necessary or not to verify the email address before user confirmation.
  * **Compliance Status**, select by default **Approve Automatically** which means no manual verification needed or **Need to Complete KYC** which means affiliates must pass compliance checks before approval.
  * **Account Status**, default statuses can be as: **Pending Approval Can not Login** where affiliates can't log in immediately and account status must be changed to active by an Admin; **Can Login Can not Send Traffic** where affiliates immediately be able to login and navigate into the platform without habilitation to send traffic (e.g., direct links); and **Active** affiliate can immediately log in and use the platform.
  * **Payment Cycle**, set as default between **Monthly** or **Weekly** payment schedules

<figure><img src="https://4110691288-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1iHXZgeTSXZwHDnWa5S8%2Fuploads%2FQUoFHYvICBkOYeuBVU8A%2Fimage.png?alt=media&amp;token=4e47e8e7-63d7-4efd-bda6-01b38c7f6076" alt=""><figcaption></figcaption></figure>

### **SMTP Default Settings**

* SMTP Default establishes the email settings to send automated emails directly from the platform.  It is important to test it to make sure it is working properly.

{% hint style="warning" %}
If SMTP is not correctly configured all the system emails (such as welcome email, reset password) wont be sent. Do not change SMTP configuration without contacting Support Team Members
{% endhint %}

* Navigate into the **SMTP Configuration**:
  * **SMTP Host**
  * **SMTP Port**
  * **SMTP Username and Password**
  * **From Email**
  * **SSL Enabled or not.**
  * **Test SMTP** **Settings**, to send testing emails to the designated email account default

<figure><img src="https://4110691288-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1iHXZgeTSXZwHDnWa5S8%2Fuploads%2FZyZBn7vc8P7fG0ObEwpY%2Fimage.png?alt=media&amp;token=3b07a008-7cca-44bd-a887-aade29178a6e" alt=""><figcaption></figcaption></figure>

### **Advanced Settings Default**

* Navigate into the **Advanced Settings** section to set some other details as:
  * Company details under **Brand Settings**: as **Brand Currency, Company** and **Label Name, Default Brand Product, Allowed Products, Sub Brands** and a box to choose between **Enabler or Disabled Client Side Input Validation for Employee**
  * Details under **Brand Site Information: Affiliate Program website title, Email’s Footer, Default Brand and available Languages, Site contact email** and **Brand full address**&#x20;
  * Details under **Brand Legal Documents: URL of Terms of Service, Privacy policy** and **Marketing guidelines**&#x20;
  * **Brand Domains Configurations: Web domain, Server, WEB API, Tracking Domain** and **important sources**

{% hint style="warning" %}
*Do not change Brand Domain configuration without contacting Support Team Members*
{% endhint %}

<figure><img src="https://4110691288-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1iHXZgeTSXZwHDnWa5S8%2Fuploads%2FTMueakFwGczzGRMXrrnG%2Fimage.png?alt=media&amp;token=3eacf2a5-704e-48f0-b82d-9be232882187" alt=""><figcaption></figcaption></figure>

<figure><img src="https://4110691288-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1iHXZgeTSXZwHDnWa5S8%2Fuploads%2FpPGBFAJTNMpXYMyRyltd%2Fimage.png?alt=media&amp;token=1b6fbe6d-ff87-4d25-8031-a2bfeee2fb8e" alt=""><figcaption></figcaption></figure>

<figure><img src="https://4110691288-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1iHXZgeTSXZwHDnWa5S8%2Fuploads%2F2zbbbsNyOs6lqn3kHd4t%2Fimage.png?alt=media&amp;token=d1757ec2-f730-4c5b-9b97-fea1e2aab0ca" alt=""><figcaption></figcaption></figure>

### **Design Default Settings**

* Navigate into the **Design** section to customize the visual appearance of your Track360 platform:
  * Set **Brand PDF Styling: Colors, Themes** and **Visual styling**
  * Update **CSS Settings**
  * Upload **Logo** ensures your affiliate portal aligns visually with your brand identity. The necessary logos for a completed operation are **PDF Logo, Website Logo, Emails Logo, Website Favicon, Website CSS File, Website background image**. And also managing existing background images

<figure><img src="https://4110691288-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1iHXZgeTSXZwHDnWa5S8%2Fuploads%2FwYPZmLCLwhfYUZSfJhDU%2Fimage.png?alt=media&amp;token=c696b8e3-56e2-4d94-80ca-96d958082ac1" alt=""><figcaption></figcaption></figure>


---

# 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://track360.gitbook.io/track360/section-5-settings/editor/5.1-brand-management.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.