In short
Four controls end or reduce a Connection: mute, archive, block and delete. Three of them change only your own copy of the relationship. Only blocking acts on the other person.
The thing to understand before you use any of them: deleting a Connection removes your side of the relationship, not the conversation. The message history is not destroyed, and the other person's copy of the relationship is not touched. Delete is how you leave. Block is how you shut a door.
On this page
Two things you might mean by “end it”
People arrive at this screen wanting one of two quite different outcomes, and the platform treats them as different operations.
“I am done with this.” You want it out of your list, off your mind, no longer part of your day. That is leaving, and delete, archive and mute are three degrees of it.
“I want this person unable to reach me.” That is a restriction on somebody else, and blocking is the only control that does it. Deleting does not do it, and choosing delete when you meant block is the single most common mistake on this page.
The reason they are separate is structural. When two people connect, each side ends up holding its own copy of the relationship — your record of them, and their record of you. Almost everything below operates on your copy alone.
What each control actually changes
| Control | What it changes | Whose side | Reversible |
|---|---|---|---|
| Mute | Marks your copy of the relationship as muted. It stays in your list | Yours only | Yes — unmute restores it to active |
| Archive | Marks your copy as archived, which drops it out of your Connections list | Yours only | Yes — nothing is destroyed |
| Block | Records a block against that person, applying in both directions, and marks the connection blocked | Acts on both | Yes — unblock |
| Delete | Removes your copy of the relationship and declines any request still pending between you | Yours only | No |
Deleting: what it does and does not do
In the App, open the Connection and choose Delete connection. In the Linxy Designer the same operation appears as Remove on the connected row — the console hands off to exactly the same code, so the two behave identically.
| Deleting does | Deleting does not |
|---|---|
| Remove your copy of the relationship | Remove the other person's copy |
| Clear the connection record between you | Delete the conversation, its history, or your membership of it |
| Decline any request still pending between you | Notify the other person that you did it |
| Optionally add a block, if you ask for one in the same step | Block on its own. Delete and block are separate actions |
| Take effect immediately, with no undo | Guarantee the person can no longer reach you |
“Cannot be undone” is literal for your copy: there is no restore and no support request that recreates it. Reconnecting means starting again with a request, an invitation link or a scan.
Blocking
Blocking is about a person rather than a conversation. It records a restriction that the platform reads in either direction — so one person blocking is enough, and there is no such thing as a half-applied block.
What it governs, verifiably: a new connection request between you is refused; the “message this person” path is refused; opening a brand channel between those parties is refused; and the platform will not bridge a fresh conversation into existence across a block. This is the control that stops somebody coming back through a new scan or a new invitation.
It is reversible, quiet, and does not announce itself. Reach for it earlier than you might think — it is the intended tool for persistence, not a last resort.
What blocking cannot do is retract anything. If you disclosed a phone number while the Connection was open, they have it. Blocking closes the platform path; it does not reach into their address book, their notes or their memory.
Muting and archiving
Both write a status onto your own copy of the relationship, and neither is visible to the other person.
Archive is the useful one for tidying. An archived relationship drops out of your Connections list, which is what you want for something finished but not regretted — a tradesperson whose job is done, a seller you dealt with once. Nothing is destroyed, so it can come back. Archive is offered on Connections with people; a brand Connection is not archived.
Mute silences a Connection without hiding it. Its messages stop sending you notifications — they still arrive and show as unread — and the Connection moves to its own Muted section of your list. Mute or unmute from the bell at the top of the Connection or from its menu. On a brand Connection, mute silences that brand’s conversation with you.
Ending it before it starts
A pending request is not a Connection. Declining one is the cheapest ending available: nothing ever opened, and the person who asked is not told why.
A decline can also record a block against the device that sent it, which is the option to use when a request feels like the first of several rather than a one-off.
Requests you simply never answer expire on their own after fourteen days. Ignoring is a legitimate ending; you are not obliged to press anything.
The temporary option
If the problem is volume rather than one person, switch off Accepting new connection requests. Existing Connections are untouched, and people who try are told you are not accepting requests right now rather than being left wondering whether their scan failed.
This is the right answer to a conference badge that worked rather too well. Switch it off on the Friday, work through what came in, switch it back on when you are ready.
Closing the doors rather than the relationship
Sometimes what you want to end is not a Connection but a way in. None of these affects anything you already hold.
| To stop… | Do this | Effect on existing Connections |
|---|---|---|
| An old printed card producing new requests | Retire that invitation Mark, or switch off Always on for it — a code that is on only while showing answers no card | None |
| An invitation link you sent in error | Revoke it from the list of open links | None. A link already claimed has produced a request, which you can still decline |
| All new requests, for a while | Switch off accepting requests | None |
| People enrolling through a commercial Mark | Change that Mark's configuration | None — channels already open stay open |
Closing a door and ending a relationship are separate operations. Doing the first while intending the second is a common and entirely silent mistake.
Symptoms, causes and fixes
| Symptom | Cause | Fix |
|---|---|---|
| You deleted a Connection and want it back | Your copy of the relationship is gone for good | Reconnect from the beginning — a request, an invitation link, or a scan |
| Somebody you deleted has requested again | Delete is not a restriction on them | Decline and block. Next time, delete and block together |
| You deleted a Connection but the conversation is still there | Expected. The conversation is a separate record from the relationship | Nothing is broken. Delete removes your side of the relationship, not the history |
| You archived and notifications continue | Archive is tidying, not silencing | Mute the conversation itself, or adjust notification preferences |
| A Connection disappeared and you did not delete it | You archived it, or the other party removed their side | Check your archive first |
| You blocked somebody and they still have your number | They read it while the Connection was open | Nothing on the platform retracts it. Treat disclosure as permanent |
| An old card still produces requests after you cleared the Connections | The Mark is still live; removing Connections does not retire it | Retire that invitation Mark, or switch off accepting requests |
| You want an organization to delete what you sent it | Not a platform function — it holds its own records | Ask them directly. Your data-protection rights apply to them |
Things people commonly get wrong
Related reading: Person-to-person Linxy Fusion, Managing Connections in the console, Consent, and what each side can see, Private channels and message privacy, and Types of Connection.