Store Syria is telling you that the authorization needs restoring, and what used to work from its side has
stopped. The shortcut that signed you straight into Lynomia Chat no longer lets you in, and Store Syria's
Lynomia Chat page asks you to connect again instead of reporting a healthy connection.

Nothing is broken and nothing is lost. The authorization that let Store Syria open your workspace was
withdrawn, and the way back is one code that you generate and nobody else can. For what happened and why
Store Syria is showing you that notice, read
[Store Syria says authorization needs recovery](store-syria-authorization-needs-recovery) first.

![Restoring a Store Syria connection](media:commerce/store-syria-recovery-en.png)

## Your workspace is safe

This is what most people want to hear before the steps, so here it is first.

| Untouched | What changed |
|---|---|
| Every contact, with its attributes and labels | Store Syria can no longer open your workspace |
| Every conversation and message, from before and during the outage | Its shortcut into Lynomia Chat stops signing people in |
| Your inboxes, your agents and their roles | Store Syria's own page asks you to connect again |
| Your settings, your automations and your reports | |

**Nothing in Store Syria changes either.** No order, no customer and no setting of yours is altered there,
and your team can carry on answering customers throughout.

Signing in to Lynomia Chat the ordinary way still works: the sign-in page, your email address, your password.
The shortcut is a convenience, not the only door. If you have never set a password because your workspace was
created for you, use **Forgot your password?** on that page.

Store data is a separate half and asks a separate question. Whether your orders are still reaching
conversations is answered in **Settings → Commerce** — see
[manage your Store Syria connection](store-syria-manage-the-connection).

## What you need first

- **Administrator** access in Lynomia Chat. Not a custom role carrying many permissions — the administrator
  role itself.
- A **Store Syria role that lets you manage Lynomia Chat**, so you can reach the page that asks for the
  code.
- A few uninterrupted minutes. The code lives for one hour, and both halves are easiest done in one sitting.

## Steps

1. Sign in to Lynomia Chat directly, with your email address and password.
2. Go to **Settings → Integrations → Connect an external platform.**
3. Under **Platform to connect**, choose **Store Syria.** A code is bound to the platform you pick here.
4. Press **Generate code.** It appears once, with the time it expires beside it. Copy it.
5. In Store Syria, open its Lynomia Chat page and paste the code where it asks for a connection code.
6. Leave the Lynomia Chat page open. The status under the code changes on its own; you need not reload.

Steps 3 and 4 both happen here: you choose Store Syria, then press Generate code.

![The Connect an external platform page, with the platform list and the Generate code button marked](media:commerce/storesyria-connection-code-en.png)

There is no repair form in Lynomia Chat and no Verify button to press afterwards. A fresh code, redeemed
once, is how the authorization comes back.

## Nobody can make the code for you

The code proves that you control this workspace, so only someone inside it can produce one.

- **Lynomia support cannot generate it.** There is no desk and no escalation that makes one for you.
- **Store Syria cannot generate it.** Their side asks for a code; it cannot mint one against your workspace.
- **Another administrator's code does not help**, because a new code retires the one before it. Two people
  working at once keep invalidating each other.

For the hour it is alive, treat the connection code as you would a password. **Never send the connection code
to anyone — not by message, not by email, not to support.** Anyone holding it can hand your workspace to the
platform it names. It is shown once, so if you lose it, generate another.

## The rules the code lives by

| Rule | What it means for you |
|---|---|
| **Administrator only** | Nobody else can generate a code, or see one that was generated |
| **One live code per account** | Generating a new code retires the one before it |
| **One hour** | It stops working an hour after you make it, used or not |
| **Single use** | The first attempt that reaches your workspace consumes it |
| **Bound to one platform** | A code made for Store Syria is refused anywhere else |
| **Your role is re-checked when it is used** | Who you are at that moment decides, not who you were |

The last two catch people out. Your workspace membership is read again at the moment the code is used, not
taken from the code. If you have stopped being an administrator in the hour since you generated it — demoted,
or removed from the workspace — the attempt is refused, **and the code is used up anyway**. A second attempt
therefore needs a fresh code: generate again rather than retyping the one that failed.

The one refusal that does *not* cost you the code is pasting it into the wrong platform. A code made for Store
Syria is rejected elsewhere and stays live for Store Syria, so you can go back and use it where it belongs.

## How to tell it worked

1. The status under the code reads **Connected to Store Syria**, and Store Syria appears again under
   **Connected platforms**.
2. The shortcut in Store Syria signs you into Lynomia Chat instead of showing a sign-in failure.
3. **Settings → Commerce** lists your Store Syria store as **Active**, and a conversation with someone who
   has bought from you shows that customer's latest 5 orders in the Commerce section.

Only the third point is about your orders, and one empty Commerce section is not a failure: matching is
exact, on a normalized email address or a phone number in international form, and names are never used.

## If Store Syria created your workspace

A workspace that Store Syria set up and manages has **no Disconnect button** under **Connected platforms**, so
this cannot arise from your side of it. If such a workspace is nevertheless asking to be connected again,
Store Syria is who to ask. Generating a code is still worth one attempt, but do not keep repeating it.

## When to ask support, and what to tell them

Ask once you have generated a fresh code, pasted it promptly, and the status still has not reached
**Connected to Store Syria** — or once two consecutive fresh codes have been refused. Before that, a new code
is faster than a ticket. Tell them two things:

- **Which store**, by the name it carries in Store Syria.
- **Roughly when it stopped working.** "Since Tuesday afternoon" rules out more causes than any other
  sentence you can write.

**Never include a connection code**, a password, or a screenshot showing either. A code in a ticket is a code
you have to retire. See [raising a ticket with Lynomia](contact-lynomia-support) for how.

## Limits

- **Administrator only**, and generating a code is recorded in the audit log.
- **One live code, one hour, single use, one named platform.** None of these is adjustable.
- **This is not a store repair.** It lets Store Syria open your workspace again; it does not connect store
  data that never connected in the first place.
- **Nothing restores it on a schedule.** Lynomia Chat does not sweep for withdrawn authorizations in the
  background, so the connection waits until you do this.

## Related

- [Store Syria says authorization needs recovery](store-syria-authorization-needs-recovery)
- [Manage your Store Syria connection](store-syria-manage-the-connection)
- [Store Syria store data did not connect](store-syria-data-did-not-connect)
- [Connect a Lynomia Chat workspace you already have](store-syria-connect-an-existing-workspace)
- [What the Store Syria integration gives you](store-syria-overview)
- [What connecting a store gives you](commerce-overview)

## If it does not work

**Store Syria says the code is invalid or expired.** It has expired, it has already been used, or it was
mistyped — all three are given the same answer, so the message will not tell you which. Generate a new one
and paste it straight away.

**The status never leaves Waiting.** The code has not reached Store Syria yet. Check it was pasted whole, and
check the expiry time shown beside it.

**It was refused, and now that code will not work at all.** A refused attempt consumes the code. That is
expected. Generate a fresh one.

**I am not an administrator.** Then you cannot do this, and nobody can do it for you from outside. Ask an
administrator of this workspace to work through the steps above.

**The shortcut works again, but there is no Commerce section.** The authorization is back and the store half
is what is missing. Work through
[Store Syria store data did not connect](store-syria-data-did-not-connect).

**I sent the code to someone.** Generate a new one at once; that retires the one you sent. If a platform has
already connected with it, disconnect it under **Connected platforms** and start again.