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

# Investments and storage

> Media from Telegram in tickets, sending files to the client, limits and quotas, storage in Postgres or S3, signals about space shortage.

Customers send anything to Telegram: photos, documents, videos, voice, gifs and stickers, all of which can be seen in the ticket correspondence, and the operator can send the file back from their side, and here's how it works and where the bytes are.

## What you see on the ticket

The images open right in the message bubble, the GIFs play themselves, the stickers are labeled "Sticker." Video and audio are uploaded by click to avoid pulling heavy files in vain. Documents are displayed with a name, size and download button.

Incoming files are not pumped out in advance: only a link to a file in Telegram is saved when you receive it, and bytes are pulled up when the operator opens the attachment. The ceiling for downloading one file: 20 MB. On the channel-account (MTProto), incoming files are not downloaded at all, only the fact of the attachment is recorded.

## Sending files by the operator

A single file is attached to one response, the text of the message is signed to it, so the delivery remains one atomic call and is safely repeated when a failure occurs.

Sending files works on a bot channel. The channel account does not support sending files to the client: the module will fail with an understandable error, the incoming files are visible as usual.

## Where the bytes lie

The files uploaded by the operators are stored by the module itself, and the method is selected in the Data Storage card:

| Method | How it works. |
| - | - |
| DB panel (Postgres) | By default. Files are in the base of the panel, a separate infrastructure is not required |
| S3-compatible storage | Objects go to your bag: AWS S3, Cloudflare R2, MinIO and compatible |

For the S3, you set the endpoint, the bucket, the region, the path prefix, and a pair of access keys. The keys are saved to the secure storage and not shown back: empty fields when saved again mean "do not change." The "Check Connection" button writes the test object into the bundle and deletes it, the error returns with the provider's response.

Switching the method does not carry old files: each file is read from where it was downloaded, you can safely go to S3 and go back without losing anything.

## Limits and quotas

The "Enclosure, MB" field limits the file size that the operator downloads. The empty value removes the limit. The "Storage attachments" tumbler controls the file retention itself.

“Enclosure quota, GB” limits the total amount of files stored. When the quota is filled, new downloads of operators are rejected until the space is vacant, and only what the module actually stores is taken into account: lazy links to Telegram media do not take up space.

## Signals of shortage of space

The indicator in the Storage card shows occupied volume, quota and free space on the disk. The module distinguishes between two levels of alarm: warning (the threshold from the Warning Threshold, % is filled or the free space is less than double minimum) and critical (quota is exhausted or free space is less than Min. free on disk, GB).

The signal comes in two ways: in the Health Center, on the incident tab, and in the Telegram notifications, the category "Storage of attachments." The alert is triggered at the level change, rather than threshing every half minute, and sends a break when you return to normal. The free disk check is only valid for storage in the database of the panel: bytes in S3 are not on the host of the panel. [health survey](https://docs.axottle.com/en/health/overview.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.