Managing Connections in the console

What the console is for, and what the App is for

Both surfaces reach the same Connections and enforce the same rules — they are not two systems that could disagree with each other. What differs is what each is good at.

The four regions of the page

Pending requests

Each request shows who asked and how the two of you met — scanned your Mark, tapped your tag, entered your code, used your invitation link — along with anything short they wrote. Approve opens the Connection; Decline closes it quietly, with no message sent to them.

The page checks for new requests on its own and refreshes when the number changes, so one arriving while you are on the page will surface without you knowing to reload. When there is nothing outstanding it says so plainly rather than showing an empty box.

The toggle at the top, Accepting new connection requests, is the master switch for inbound. Switch it off and people trying to reach you are told you are not accepting requests right now — which is better than a silent failure they will retry five times. Existing Connections are untouched.

Reviewing what you share, across everybody

Each connected row carries a What they can see control listing the individual fields — name, email address, phone number, photo — with your display name shown as always shared and not switchable.

This is the caller's side of the arrangement: what you reveal to that person, not what they reveal to you. The two are separate settings held on separate sides, and nothing you do here asks them for anything or notifies them of a change.

Worth doing every few months, and worth doing after any event. A phone number you shared with somebody in a hurry in March is still shared in November unless you go and look.

Your card

The card is what a person sees when they reach your invitation Mark, before any Connection exists. Four fields are editable here: display name, headline, a photo address, and a context note with an optional date after which it stops showing.

The context note is the most useful and least used field on the page. “At the Munich show, stand 4B, until Thursday” makes a scan from a stranger comprehensible, and expires by itself so you are not still advertising a trade show in August.

Building an invitation Mark

An invitation Mark is a Linxy Mark that belongs to you personally and does nothing except carry connection requests. You build it here rather than in the ordinary Mark editor.

1. Choose a background
   From the published set. This is the carrier that holds the invisible signal, which is why it is not a free-for-all — the backgrounds have been tested to read reliably.
2. Add your logo or icon
   Upload artwork or pick from the Linxy set. You can also choose no logo at all.
3. Set shape and size
   Circle or rounded square, sized against the background. The preview shows it at full size so what you see is what will print.
4. Check the strength reading
   It tells you how robustly the finished composite reads before you commit to it.
5. Create and check the scan
   The finished composite is scanned before anything is saved. If it does not read, nothing is stored — which is the behavior you want, because the alternative is discovering it at the print shop.

You can hold up to ten active invitation Marks, with one designated live — the one new requests come through. Keeping several is genuinely useful when a card design, a badge and a sign are all in circulation. Make live switches which one is current; Retire removes one from the set, and if it was the live one the next oldest is promoted so you are never left without one.

Invitation Marks do not appear in your ordinary Marks list, and cannot be edited or repurposed there. That is the same protection Marks backing a LinxyPass site login receive, and for the same reason: something that other people's access depends on should not be editable by accident.

Where the Mark leads

Both of the non-default options fail gracefully rather than dead-ending. A bio page that is later deleted, or a custom address that is malformed, falls back to showing your card — so a scan never lands on an error page in front of somebody you were trying to impress.

Invitation links

An invitation link is the path for people you can already reach: create one, label it if you like, copy it, and send it. Each link works once and expires after seven days, and you can revoke any open one from the list before it is used.

The single-use rule is the feature, not a limitation. A link that works once cannot be forwarded into a group chat and used by twelve people, so a link you sent to one person can only ever connect that person.

Brand channels are somewhere else

This page is about you as a person. Conversations with people who connected to your brand through one of your commercial Marks live in that Mark's messaging console, not here — because they belong to the Mark, can be staffed by several people, and behave differently in every respect that matters.

If you use the platform both ways — a company Mark on your packaging and an invitation Mark on your own card — expect two separate places, and do not look for your customers in this list.

Symptoms, causes and fixes

Things people commonly get wrong

Related reading: Person-to-person Linxy Fusion, Consent, and what each side can see, Ending a Connection, Brand-to-consumer Linxy Fusion, and Creating a Linxy Mark.