> For the complete documentation index, see [llms.txt](https://docs.hesh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hesh.app/manuals/settings.md).

# Settings

{% hint style="info" %}
Page is under construction
{% endhint %}

## Overview

The Settings page in HESH provides a centralized platform for configuring system-wide options that affect both web and mobile apps. It enables customization of company-specific information, task management parameters, production deadlines, and user interface behavior to align with operational needs.

By exploring this page, you will understand how to configure company-specific settings, including auto-filled and default options, manage branding elements like logos and abbreviations for seamless identification, and set deadlines, rewards, and task card views for all users. You will also learn how to establish working schedules, notification rules, and the logic for sorting tasks based on priorities and deadlines. Moreover, the page explains how to customize the number of managers assigned to productions.

## Key Features

1. Flexible management of company branding elements, including logo uploads, order key abbreviations and currency. 
2. System-wide configuration of options such as currency, language, production deadlines, and task card views.
3. Tools for managing task corrections, reporting periods, and rewards after deadlines. 
4. Settings for user schedules, day-off management, and system notifications.

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

The following three articles will describe each of the tabs and the settings they have.


---

# 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://docs.hesh.app/manuals/settings.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.