In short
Your connect code is your own Invitation Mark, made in the Linxy App under Connections. You show it on your phone or on a tablet at a table; the other person scans it with the App, asks to connect, and you approve. No number, no link to send.
Two things people miss at first. The code is on only while you are showing it — a screenshot or a forwarded picture of it does nothing — and every request still comes to you to approve. The code is free on every plan; what the plan limits is how often you change its look.
On this page
Making your code
Open Connections › Add connection › Show my connect code. The first time, you pick a look:
- A color from the library. The Mark is embedded in the color itself; the surface carries a faint paper grain so the camera has something to read.
- Your photo — from the camera, your photo library or My Files. You fit the picture inside a square frame; what is inside the frame is exactly what gets marked. Photos with texture and detail scan best; flat white areas and large areas of skin tone scan least well. If a photo cannot carry the Mark the App tells you and keeps your previous code.
- A logo, optionally, placed small in the bottom-right corner — your Display-branding banner or an upload. The logo is added after the Mark is embedded and the code is checked again, so it never weakens the scan.
The code is made at the exact pixel size of the screen you are on, and shown back at that size, one image pixel to one screen pixel. That is why a code made on your phone is strongest on that phone, and why a tablet gets its own, larger code when you make one there.
Showing it: full screen and Table display
The fastest way: tap Linxy Connect Code on your Home screen. Your code opens full screen straight away, ready to scan. If you have not made a code yet, the tile opens the screen that makes one. You can hide the tile under Settings › Home screen.
Show full screen to scan fills the width of the screen with the code, keeps the screen awake, and puts your name and headline above it. Tap anywhere to close. This is the everyday way: you hold the phone up, they scan.
Table display is for a tablet or a phone on a stand at a show, a booth or a desk. The code sits alone on a white pane; beside it is a pane you can brand — a banner or logo, your photo or initials, your name and headline, a tagline and a context note such as “booth 214”. Nothing is ever drawn over the code itself. The page follows the device if you turn it, and it closes with a tap-and-hold so somebody reaching for the screen does not close it by accident.
What is shown around the code comes from Settings › Display branding. Changing it never changes the code.
When it works, and when it does not
By default your code answers only while the App is showing it — on the full-screen page or in Table display. Close the page and the code is off. A screenshot, a photo of your screen, a forwarded image or an old scan in somebody's history produces nothing, and nobody can put a request in front of you from it.
A request also has to follow a real read. The platform records when a camera scan or a tag tap actually happened, and only accepts a connection request that comes within a few minutes of one. A link opened from a message or a browser is not a read.
| Setting | What it does | Use it when |
|---|---|---|
| Only while I’m showing it | The default. On while the code is on screen, off otherwise | Always, unless one of the two below applies |
| Always on | The code answers at any time, from any copy of the image | You hand the image out — a printed card, an email signature, a poster |
| NFC tags always work | Tags you wrote keep working while the screen is off, independently of the switches above | A tag on a desk, a badge or a door |
Switching Always on is deliberate: once a copy of the image is out there, anyone who scans it can ask to connect, and the only way to stop that is to retire the code. Retiring is free at any time.
NFC tags
Write NFC tag on the code screen writes a blank NTAG tag with your invitation. The tag carries an opaque token, never your name or your details. Somebody who taps it with the Linxy App gets the same offer to connect as a scan would, and the request reaches you marked “Tapped your NFC tag”. Without the App, a tap opens a page that offers to open Linxy — nothing more.
Each tag has a name and appears under Settings › NFC tags. Remove a tag there and it stops working at its next tap; the physical tag can be rewritten later. Tags are not affected by the only-while-showing rule unless you switch off NFC tags always work.
Changing the look, and what it costs
New look makes a fresh code and retires the previous one the moment the new one is live. Each new look is a change. The first code is free of the count; after that your plan sets how many changes you have per rolling 30 days, shown on the code screen as “N changes left this month”. When the count is used up the App tells you when the next change opens.
Retiring your code — from Settings or the web — is always free and does not count. Make a new one whenever you like within your plan.
What the other person sees
They open Linxy › Scan and point at your screen or tap your tag. The App shows your name and offers to connect; they confirm. A request lands in your Pending requests with how they reached you, and nothing is connected until you accept. Declining is silent. Blocking stops a person coming back through a new scan.
If your code is not being shown at that moment, their App says the invitation is not active right now and offers nothing — it does not reveal who you are.
The Invitation Mark on the web
Your code is a Linxy Mark with the Invitation role. Opening it in the Linxy Designer shows a compact editor made for invitations: the image, whether it is live right now, scans and connections, Download, Retire, the three switches above, your NFC tags and a private label. The role is fixed — an invitation cannot be turned into a content Mark — and the controls that belong to content Marks (destination, routing rules, geofence, microchannels, messaging, transfer) are not offered. Invitation Marks are also kept out of your ordinary Marks list on purpose.
Symptoms, causes and fixes
| Symptom | Cause | Fix |
|---|---|---|
| They scan and nothing happens | Your code is not on screen, so it is off | Open Show full screen or Table display and let them scan again |
| “Scan or tap the invitation in person to connect” | They tapped Connect without a real read in the last few minutes — usually from a link or an old item in their history | Show the code and have them scan it now |
| Scans only read from very close | The code was made on another device with a different screen size, so it is being scaled | Make the code on the device you show it from |
| “This photo can’t carry a mark” | Too little texture for the Mark to survive | Choose a photo with more detail, or a color |
| New look is greyed out | Your plan’s changes for the month are used | Wait for the date shown, or upgrade. Retiring is still free |
| A tag still works after you removed it | The phone read it before the removal reached the platform | It stops at the next tap |
| A printed card stopped producing requests | The code is on only while showing | Switch on Always on for that code, knowingly |