# General Settings

The General Settings page contains application-wide configuration: license management, code settings, and Telegram version parameters.

![Settings (top)](/files/0JvBIIcbxM0gMNYX6Jxr)

![Settings (bottom)](/files/Lstw7dDpMw3fhTGwpl9D)

## License

At the top of the page, the **License** section shows:

* **Status** -- whether your license is valid and how many days remain (e.g., "Valid -- <user@example.com> (289 days left)")
* **License Key** -- your full license key with a copy button

To activate or change your license:

1. Paste the new key in the license field
2. Click **Save**

{% hint style="info" %}
Your license is tied to your hardware. If you move to a new computer, contact support to transfer your license.
{% endhint %}

## Code Settings

The **Code Settings** section controls `auth.sendCode` flags per platform. These are technical parameters that affect how Telegram sends verification codes during registration.

### iOS Flags

| Flag                    | Description                        |
| ----------------------- | ---------------------------------- |
| **allow\_missed\_call** | Allow verification via missed call |
| **allow\_firebase**     | Allow Firebase-based verification  |

### Android Flags

| Flag                    | Description                                       |
| ----------------------- | ------------------------------------------------- |
| **allow\_flashcall**    | Allow verification via flash call                 |
| **current\_number**     | Indicate the phone is the device's current number |
| **allow\_app\_hash**    | Include app hash in verification request          |
| **allow\_missed\_call** | Allow verification via missed call                |
| **allow\_firebase**     | Allow Firebase-based verification                 |
| **unknown\_number**     | Mark the number as unknown to the device          |

Each flag has a toggle switch (on/off). The default values work well for most cases.

{% hint style="warning" %}
**Do not change these settings unless you know what you are doing.** Incorrect flag combinations can cause registration failures. The defaults are tested and match official Telegram client behavior.
{% endhint %}

Click **Save** after making changes to Code Settings.

## Telegram Versions

The **Telegram Versions** section lets you configure what Telegram layer and app versions the application uses when connecting to Telegram. Each platform (iOS, Android, Desktop) has **independent settings**:

### Per-Platform Settings

| Field                    | Description                                                          |
| ------------------------ | -------------------------------------------------------------------- |
| **iOS Layer**            | The Telegram API layer number for iOS connections (e.g., 224).       |
| **iOS app\_version**     | The version string for iOS connections (e.g., `12.5 (32473)`).       |
| **Android Layer**        | The Telegram API layer number for Android connections (e.g., 224).   |
| **Android app\_version** | The version string for Android connections (e.g., `12.5.1 (65802)`). |
| **Android perf\_cat**    | Performance category for Android devices.                            |
| **Desktop Layer**        | The Telegram API layer number for Desktop connections.               |

Click **Save** after making changes.

{% hint style="info" %}
These versions are updated with each MVS Web release. You generally do not need to change them unless specifically instructed by support.
{% endhint %}

## System Info

At the bottom of the page, the **System Info** section shows:

| Field       | Description                                                    |
| ----------- | -------------------------------------------------------------- |
| **Version** | Current MVS Web version (e.g., 1.9.1)                          |
| **Uptime**  | How long the application has been running since the last start |


---

# Agent Instructions: 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:

```
GET https://mvs-3.gitbook.io/mvs-docs/settings/general.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.