> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lekalao.com/llms.txt
> Use this file to discover all available pages before exploring further.

# General settings and maintenance

> Name, public URL, default sender, and how healthy Lekalao is.

## General settings

**Settings → General**. These settings belong to the current team.

### Application

<ParamField path="Application name" type="text">
  The name that appears in the e-mails and on the public pages when the brand
  gives no other.
</ParamField>

<ParamField path="Public URL" type="URL">
  The base of the links sent to subscribers: unsubscribe, click tracking, web
  version. Leave it empty to use the installation's own address. Useful when
  Lekalao answers on a different domain from your e-mails, say
  `https://news.mybakery.example`.
</ParamField>

### Default sender

**Sender name**, **Sender address** and **Reply-to address** (optional) prefill new lists and serve the e-mails that name none of their own. Each list may then have its own.

<Note>
  The sender address has to be on a [verified
  domain](/deliverability/domains), or your e-mails risk the junk folder.
</Note>

### Organisation

<ParamField path="Postal address" type="text" required>
  Your organisation's address, which the law asks for in every marketing e-mail. **No campaign goes out while it is missing.** Put it in your templates with `{{ organisation.address }}`.
</ParamField>

### Contacts

<ParamField path="Delete unconfirmed subscribers after (days)" type="number">
  People who never clicked the confirmation link are deleted after that many
  days, every night. Leave it empty to keep them.
</ParamField>

## Maintenance

**Settings → Maintenance** answers the question "is everything running?". At the top, when the scheduler last ran.

### Is everything running?

| Check           | In good health             | Otherwise                                                                                          |
| --------------- | -------------------------- | -------------------------------------------------------------------------------------------------- |
| **Scheduler**   | "Running."                 | It never ran, or not for several minutes: scheduled campaigns, automations and purges are waiting. |
| **Queues**      | How many jobs are waiting. | The queue cannot be reached (Redis), or many jobs are waiting: there are not enough workers.       |
| **Failed jobs** | "None."                    | Jobs failed: read them in Horizon.                                                                 |
| **Mailers**     | All ready.                 | No mailer, or some never tested or failing: send a test e-mail.                                    |
| **Campaigns**   | "Nothing stuck."           | Campaigns have been "sending" for more than six hours: the workers are probably stopped.           |

Each problem comes with what to do about it. On an online offer, tell the support; when you host it yourself, see [Monitoring](/self-hosting/monitoring).

### Queues

How many jobs are waiting in each queue. **Open Horizon** leads to the workers' dashboard (for the installation's administrators).

### What is stored

How much of each kind of data there is: subscribers, campaign e-mails, transactional e-mails, provider feedback, running automations.

Every night, the detail of opens, clicks, transactional e-mails and webhook calls older than 365 days is deleted. **Purge now** does it at once. The campaigns' statistics stay: only the detail behind them goes.