You already run a Lynomia Chat workspace, with your inboxes, your agents, your contacts and every
conversation they have had. You want Store Syria's orders beside those conversations, and you do not want a
second workspace sitting next to the first.

This is the path for that. You generate a **connection code** in Lynomia Chat, paste it into Store Syria, and
Store Syria connects to the workspace you already run. Nothing in that workspace is replaced.

If you do not have a workspace yet, do not start here: press **Create workspace** in Store Syria and let it
make one for you — see [set up Lynomia Chat from Store Syria](store-syria-set-up-from-store-syria), which
is shorter and has nothing to copy.

## What you need first

- **Administrator** access in Lynomia Chat — the administrator role itself, not a custom role carrying a lot
  of permissions. A code lets an outside platform into the whole workspace, so only an administrator makes one.
- A **Store Syria store**, and a Store Syria role that lets you manage Lynomia Chat.
- A plan that **includes store data**. Without it your workspace can still be connected, but the half that
  reads your orders is refused.
- A store that is **not already connected** to another Lynomia Chat workspace.
- **Store Syria offered on your installation**, so that it appears in the platform list below. If it is not
  there, it is switched off there, and that is not something you can change.

## Steps

1. Go to **Settings → Integrations → Connect an external platform.**
2. Under **Platform to connect**, choose **Store Syria.** The code works only for the platform you pick here.
3. Press **Generate code.** It appears once, with the time it expires beside it. Copy it.
4. Paste the code into Store Syria where it asks for a connection code.
5. Copy the short-lived **verification code** Store Syria shows you in return. It appears once.
6. Give that verification code to Store Syria support. Their approval is what finishes the connection.
7. Leave the Lynomia Chat page open. The status under the code changes on its own; you need not reload.

Steps 1 to 3 all happen on one page, and this is that page before you have generated anything.

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

## While Store Syria's team reviews it

Pasting the code does not finish the job on its own. Store Syria shows **Awaiting approval** on its own page
while the claim is outstanding: Lynomia Chat has already confirmed that you control the workspace, and what
is left is Store Syria support approving the connection. That is a decision someone makes, not a check
that completes by itself, so reloading the page does not move it along. The status on this page tells you
when Store Syria has used your connection code, not when the approval has gone through — that shows on
Store Syria's own page.

The verification code in step 5 is Store Syria's own, and it is the one code you are meant to pass on:
support use it to match the claim to you. It is **not** the connection code you generated in Lynomia Chat,
and the two must never be mixed up — the verification code is handed over, the connection code never is. If
the verification code lapses before the claim is approved, start again: generate a fresh connection code in
Lynomia Chat and paste it into Store Syria.

## Treat the connection code as a key

For the hour it is alive, the connection code is the one thing that proves you control this workspace, and
anyone holding it can hand that workspace to the platform it names. **Never send the connection code to
anyone — not by message, not by email, not to support.** It is shown once, so if you lose it, generate a new
one. Store Syria's verification code, above, is the one code you do give to support.

## The rules the connection 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 |

That last rule matters more than it looks. If you leave the workspace, or your role changes to something other
than administrator, in the hour between generating the code and Store Syria using it, the connection is
refused — and the attempt still uses the code up. Put your role right first, then generate a fresh code.

## What the page tells you while you wait

| Status | What it means | What to do |
|---|---|---|
| **Waiting for Store Syria to use the code** | Live, and nothing has happened yet | Paste it into Store Syria |
| **The code has been used** | Store Syria has your connection code | Carry on in Store Syria: give support the verification code |
| **Connected to Store Syria** | Lynomia Chat has accepted the code — it does not yet mean Store Syria has approved | Finish the approval in Store Syria, then check your store data, below |
| **That code expired before it was used** | The hour ran out | Generate a new one |
| **This connection was ended** | It was disconnected from one side or the other | Generate a new code |

## When Store Syria refuses the code

**"That connection code is not valid, has already been used, or has expired."** Expired, already used and
mistyped are deliberately given the same answer, so the message alone will not tell you which. Generate a new
code and paste it straight away rather than retyping the old one.

**"That connection code was created for a different integration."** You pasted a code minted for another
platform. Nothing is lost: it is **not** used up by this, and it stays live for the platform it was made for.
If it was meant for Store Syria, go back, choose Store Syria under **Platform to connect**, and generate
again.

**The store is already connected to another workspace** (`installation_claimed_elsewhere`). One Store Syria
store belongs to one Lynomia Chat workspace, so a store connected elsewhere is refused rather than moved.
Disconnect it in the other workspace first, then connect it here.

Connecting your workspace and connecting your store's data are two separate things, so the code can succeed
while your orders are still missing. Every reason the store half is refused is in
[Store Syria store data did not connect](store-syria-data-did-not-connect).

## Nothing in your workspace is replaced

Your inboxes, contacts, conversations, agents and settings all stay exactly as they are. No inbox is created
or renamed, no contact is rewritten, no history is touched, nobody is added and no role is changed.

What is added is read-only: a **Commerce** section beside a conversation, showing the store customer the
contact was matched to and that customer's latest 5 orders — see
[what connecting a store gives you](commerce-overview).

## How to tell it worked

1. The status reads **Connected to Store Syria**, and Store Syria is listed under **Connected platforms**.
   Store Syria no longer shows **Awaiting approval**, because support has approved the claim.
2. **Settings → Commerce** lists your Store Syria store as **Active.** This is the real test: it is the half
   that carries your orders.
3. A conversation with someone who has bought from you shows their recent orders in the Commerce section.

One empty Commerce section does not mean the connection failed. Matching is exact, on a normalized email
address or an international phone number, and names are never used.

## Who can do this

Generating the code is an **administrator** action in Lynomia Chat, recorded in the audit log, as are
disabling, disconnecting and replacing credentials later. Pasting it needs a Store Syria role that may manage
Lynomia Chat. Any agent who can see a conversation sees the Store Syria orders in it.

**This is the one path you cannot finish on your own.** Store Syria support approve the claim, and until they
do it stays at **Awaiting approval**. Nothing you can press in either system moves that along, and there is
no setting of yours that skips it. If you would rather not wait on anyone, Store Syria can set a fresh
workspace up for you instead — see
[set up Lynomia Chat from Store Syria](store-syria-set-up-from-store-syria).

## Limits

- **Administrator only, one live code, one hour, single use, one named platform.** None of these is adjustable.
- **One store, one workspace.** A store connected elsewhere is refused rather than moved.
- **Read-only.** Lynomia Chat reads Store Syria and never writes to it. No order actions are planned.
- Because this workspace is yours rather than one Store Syria created, **Disconnect stays available** under
  **Connected platforms** — see [manage your Store Syria connection](store-syria-manage-the-connection).

## Related

- [What the Store Syria integration gives you](store-syria-overview)
- [Set up Lynomia Chat from Store Syria](store-syria-set-up-from-store-syria)
- [Open Lynomia Chat from Store Syria](store-syria-open-lynomia-from-store-syria)
- [Manage your Store Syria connection](store-syria-manage-the-connection)
- [Store Syria store data did not connect](store-syria-data-did-not-connect)
- [What connecting a store gives you](commerce-overview)

## If it does not work

**Store Syria is not in the platform list.** It is switched off on your installation. Ask whoever runs it.

**The page says Connected, but there is no Commerce section.** The workspace half succeeded and the store half
did not. Work through [Store Syria store data did not connect](store-syria-data-did-not-connect).

**The status never leaves Waiting.** The code has not been used yet. Check it reached Store Syria intact, and
check it has not expired — the expiry time is shown beside the code.

**Support asked me for my connection code.** They should not, and nobody else should either. What support
needs is the verification code Store Syria showed you after you pasted — not the code you generated in
Lynomia Chat. Refuse, then generate a new connection code, which retires the one they asked about.

**Store Syria still says the claim is awaiting approval.** Support has not approved it yet, or the
verification code expired before they did. Check that support has the verification code. If it has expired,
generate a fresh connection code here and paste it again to start a new claim.

**I think someone else has seen the connection code.** Generate a new one at once; that retires the old one. If a
platform has already connected with it, disconnect it under **Connected platforms** and start again.