In short
The Connections screen is one list holding two different kinds of relationship: organizations you have joined, and people you have connected with directly. You can filter between them, see which requests are waiting, add a new connection three different ways, and open any of them to message, call, take notes or end the relationship.
The part that is easy to miss is the badge on each row. It tells you who can read that conversation — and it is not a setting you chose, it is a property of the kind of connection you have. Person-to-person is always server-blind. A brand channel is readable by the brand’s staff unless the brand has escalated it. That distinction decides what belongs in each conversation, and no amount of care with wording changes it.
On this page
- What the list actually contains
- Filters, and where muted connections go
- Three ways to add a connection
- The trust badge, and why it is not a setting
- Why it asks for your face or fingerprint
- Inside a connection
- Mute, archive, block, delete
- The card, the bar and the search field
- Symptoms, causes and fixes
- Things people commonly get wrong
- Calls, missed calls and Recent calls
What the list actually contains
Two sources are merged into the one screen. The first is your relationships — every connection formed through a Mark, an NFC tap, a code, an event, or a direct request. The second is the set of organizations you have joined as a member. They arrive from different places and are shown as one list because, from where you are standing, they are the same thing: people and organizations you have a live relationship with.
Each row carries the other party’s name, a trust badge, and an unread count where there are messages waiting. Pull down to refresh, and the pending requests are refreshed at the same time so the two never disagree.
Filters, and where muted connections go
| Filter | Shows |
|---|---|
| All | Everything |
| Brands | Organizations only |
| People | People, including anyone you connected with at an event |
Muted connections are not removed from the list. They are collected into a dimmed section at the bottom, under a Muted connections heading, whichever filter you are on. That is deliberate: muting is about notifications, not about disappearing, and a connection you can no longer find is a connection you cannot end.
Above the list, a badge on the inbox icon counts requests waiting for you, and an amber banner appears when there are incoming ones. The badge stops counting past ninety-nine and shows 99+ from then on.
Three ways to add a connection
Add connection in the header opens a panel with all of them, plus any requests currently in flight in either direction — waiting for you, and ones you sent. Those sections are hidden entirely when there is nothing outstanding, so the panel stays quiet most of the time.
| Route | How it works | Best for |
|---|---|---|
| An invitation link | Mint one, copy it, send it however you like. It is single-use and expires after seven days | Someone not in front of you |
| Scan a Linxy Mark | Point the camera at a printed or on-screen Mark | Meeting in person, or a printed card |
| Tap an NFC tag | Hold the phone near a Linxy-enabled sticker, card or tag | The same, without a camera |
Separately, the keypad icon in the header takes a code an organization has given you and joins you to it directly. That is the brand route, and it does not go through a request.
The trust badge, and why it is not a setting
The badge appears both on the row in the list and at the top of the connection itself, so the two never drift apart. On a Sealed channel there is an extra step available: a safety number that both of you can compare. It is worked out on your own device from the conversation’s own key material, with nothing asked of the server, and once you have checked it against the other person’s the connection shows as verified.
Why it asks for your face or fingerprint
Opening Connections or your Messages list asks you to prove it is you, and so do opening a connection’s profile, opening a conversation (including from a notification), and starting a voice or video call — calling back from Recent calls included. This is separate from the check the App makes when it opens. When the check is for one connection, the prompt names the person, so you always know what it is about to open.
This exists for a specific and unglamorous threat: an unlocked phone on a table. Signing in once, hours earlier, is not evidence that the person now holding the handset is you. The check is asked for fresh, and the answer is good for a short while afterwards so that reading a message and then calling back does not mean two prompts.
| Behavior | Detail |
|---|---|
| How long a check lasts | Five minutes |
| What cancels it early | The App being in the background for more than thirty seconds |
| If you decline the prompt | Nothing opens, and you are told verification is needed. Nothing is broken |
| If the phone has no biometric set up | You are asked to enable Face ID or Touch ID in the phone’s settings and try again |
Inside a connection
A connection with a person opens on Timeline, with Info beside it. An organization’s opens on Feed — its own posts — followed by Timeline and Info. The Timeline is the history of every touchpoint that contributed to the relationship — calls, scans, taps, events — gathered into one sequence rather than kept in separate places.
Across the top sit Message, Call and Video. Calls run on the same channel the conversation uses, which is why a call can be unavailable on a connection that has no conversation behind it — an organization you joined without an account, for instance. The App says so rather than failing quietly.
The Info tab holds your own notes and tags about this relationship, and the list of fields each side has agreed to share. Notes are private annotations for you. They are not visible to the other party and never form part of the conversation.
Mute, archive, block, delete
| Action | What it actually does | Reversible? |
|---|---|---|
| Mute | Stops its notifications — messages still arrive and show as unread. It stays in the list, in its own Muted section | Yes, from the same menu |
| Archive | Takes it out of the working list and out of the counts. The relationship itself is unchanged. Offered on Connections with people, not on brands | Yes |
| Block | Stops the other party reaching you. One side blocking is enough — it does not need to be mutual | Yes, from your blocked list |
| Delete | Removes your copy of the relationship, declines anything pending, and optionally blocks | No |
The card, the bar and the search field
Each Connection is drawn as a card the full width of the list. Where the other side has supplied artwork — a Brand’s reviewed image, or a person’s photo set under How you appear — it runs corner to corner; where they have not, the card is a field of their color. The name and the trust badge are always drawn by the App itself, over whatever artwork arrived, so a card can never carry a badge it did not earn. Your own card, and how to give it a photo, a mark and a color, is covered in How you appear; the icon on the Connections bar opens that screen.
Along the bottom of every card sits a bar carrying only the paths that exist for it:
| Segment | Does | Present on |
|---|---|---|
| Connect | Opens the conversation — the same as tapping the card | Every card |
| Website | Opens the Brand’s site in your browser, as a visitor | Brands with a site address |
| Sign in | Runs One-Tap and opens the site signed in as you | Brands you enrolled with through LinxyPass |
Long-pressing a card that has a Sign in segment offers to pin that Brand to your home screen. Both are described in One-Tap sign-in and Pinning a Brand to your home screen. The shelf of recent sign-ins that once sat on this screen now lives on the LinxyPass screen, which is where signing in belongs.
Above the list is a search field. It matches names only — Brand and person names — not message text, and it filters the list in place as you type; clear it and the full list returns. Filters and search combine, so you can search within People or within Brands.
Inviting someone to Linxy
On Add connection, Send an invite makes a personal link for one person and writes the message for you. Choose Text, Email or More… to send it; you can change the words first.
- The link works once and expires after 7 days. Invites you sent shows whether each person has joined, and Cancel stops a link straight away.
- Someone without the app sees your name, a line about Linxy and the App Store and Google Play buttons. After installing, they tap your link again and the app opens to your invitation.
- Someone who already has the app is asked to confirm. On Android the link opens the app directly; on iPhone it may open a page first, where I already have Linxy, open the invite takes them into the app.
- Once they confirm, you are connected in a Private conversation only the two of you can read.
You can also invite anyone who sent you files with your drop link: open My drop link and use Invite to Linxy next to their name.
Symptoms, causes and fixes
| Symptom | Cause | Fix |
|---|---|---|
| Somebody you connected with is not in the list | Their request is still pending, or yours is | Check the inbox icon. Requests are not connections yet |
| A connection has vanished from the list | Muted connections move to the bottom; archived ones leave the working list | Scroll down, and check the archive |
| You are asked for Face ID repeatedly | The App has been in the background between actions | Expected above thirty seconds. Within it there is no second prompt |
| Verification needed to open this conversation | The biometric prompt was dismissed | Tap through again and accept it |
| Call is unavailable on a connection | There is no person on the other side to call — an organization, or a device-only record | Use messaging instead where it is offered |
| You sent an invitation link and nothing happened | It is single-use and expires after seven days | Mint a fresh one. An expired link cannot be revived |
| You deleted a connection and they can still message you | Delete removes your side of the relationship. It is not a block | Block them |
| A brand replied under a different name | The channel is staffed | Expected. The relationship is with the organization |
Things people commonly get wrong
Related reading: Types of Connection, Consent, and what each side can see, Ending a Connection, Private channels and message privacy, and Messages in the App.
Calls, missed calls and Recent calls
Every call you make or receive in Linxy is kept in your own call history. Only you see your side of it.
- Recent calls — tap the phone button at the top of Connections. It lists every call, newest first, grouped by day, with All and Missed. Tap the button at the end of a row to call back; you confirm it is you first, the same as calling from a Connection.
- Missed calls — the phone button shows how many you have not looked at yet, and the Connection’s card reads “Missed audio call” (or video) with the time. You also get a notification, unless the Connection or its conversation is muted. Opening Recent calls clears the count.
- A Connection’s Timeline — open the Connection and choose Timeline: its calls by day (“Outgoing video call · 4 min”, “Missed audio call”, “No answer”, “Declined”), then its other activity, then when and how you connected.
A Connection with a person has two tabs, Timeline and Info. A brand Connection also has Feed, for the brand’s own posts. Call history starts from October 6, 2026; calls before that were not recorded.
Calls ring only on a phone that is signed in to your account. Signing out with Logout in Settings stops calls ringing that phone, and signing in again turns them back on.