> For the complete documentation index, see [llms.txt](https://conso-1.gitbook.io/conso/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://conso-1.gitbook.io/conso/account-and-onboarding/conso-passport.md).

# Conso PASSPORT

Your identity safety layer—link accounts, protect rewards, and recover access if a Telegram account is lost.

PASSPORT is Conso’s identity safety layer. It helps you protect and recover value tied to your Conso identity by letting you link a verified sign-in method and connect multiple PASS IDs under one protected profile.

PASSPORT is designed for the real-world Telegram scenario: users may have more than one Telegram account over time, but still want a consistent way to protect assets/rewards and prove ownership.

<mark style="background-color:$primary;">**What PASSPORT does**</mark>

PASSPORT provides three core capabilities:

<details>

<summary><mark style="color:$primary;">Link a recovery method (proof of ownership)</mark></summary>

You can link at least one verified method (such as Apple / Google / Email / X / TON wallet, depending on what Conso enables).

This linked method becomes your proof of ownership and supports recovery.

</details>

<details>

<summary><mark style="color:$primary;">Connect PASS IDs naturally</mark></summary>

PASSPORT is built around a key principle:

You don’t “manage multiple PASS IDs” manually in daily usage—Conso handles linking when it can, and only asks you to confirm when necessary.

</details>

<details>

<summary><mark style="color:$primary;">Protect high-risk outflows (rewards safety gate)</mark></summary>

For certain high-risk actions—especially actions that could spend system reward balances—PASSPORT may require an upgrade step that cannot be skipped.

This is to prevent reward abuse and protect ownership in edge cases (multi-account, account loss, suspicious state).

</details>

<mark style="background-color:$primary;">**How PASSPORT works**</mark>

**Link first, then Conso can recognize you later**

When you link a verified method, PASSPORT can later help Conso recognize that:

* a newly created PASS ID (from a new Telegram login) belongs to the same person, and
* should be connected back to your protected profile

**Primary PASS**

When multiple PASS IDs exist, PASSPORT may designate one as the Primary PASS.

This allows Conso to apply clear ownership rules for items that require stricter accounting (especially reward outflows).

{% hint style="warning" %}
**Important Notes**

To keep reward systems abuse-resistant, PASSPORT may enforce rules such as:

* Reward balances being tied to a Primary PASS for outflow eligibility
* In multi-PASS scenarios, some reward balances under non-primary PASS IDs may not be eligible for outflow once you finalize linking and proceed

Conso should always surface these rules clearly in-product before you confirm.
{% endhint %}

***

#### FAQ

<details>

<summary>Is PASSPORT a new ID that replaces PASS ID?</summary>

No. PASS ID(s) remain your Conso identity identifiers. PASSPORT is the safety layer that links and protects them.

</details>

<details>

<summary>Do I need PASSPORT to use Conso?</summary>

No. PASSPORT is recommended when you care about recovery and protected outflows (especially rewards).

</details>

<details>

<summary>If I lose my Telegram account, can PASSPORT help?</summary>

That is the purpose: you can log in with a new Telegram account (new PASS ID) and use your linked method to re-connect to your protected profile.

</details>