NFC devices

NFC devices is your organization’s tag fleet: every Lynqu tag your team carries, who holds it, which card it opens, and how often it gets tapped. It is free with every plan, under Organization → Settings → NFC devices.

Provisioning, assigning, locking and removing tags are admin actions (on Enterprise, the NFC devices capability in Roles & permissions). Managers see the batch summary rows; every member sees the tags they hold.

If you are after your own tags rather than the team’s, see NFC tags.

Provision a batch

A batch is any number of tags created in one go. Set a name prefix and the tags are numbered: Booth 1, Booth 2, and so on. The wizard shows the maximum for one batch.

Choice	What it does
A number of tags	Mint that many tags, all opening the card you pick, or Decide later and point them when you hand them out.
One per member	Mint one tag per selected member, named after them and pointed at their own team card.
Pre-encoded stock	For tags that will sit in a box before anyone owns them. Each gets a printed claim code, and a tap shows a claim page until someone uses it.
Overridable	For events. Each member who taps a tag can point it at their own team card. See Event batches.

When the batch is ready you download a CSV with each tag’s link, for whoever encodes the plastic. For pre-encoded stock the same file holds the claim codes, and it is the only copy: Lynqu stores the codes hashed and cannot show them again.

Pre-encoded stock and overridable are alternatives, not a combination, and one tag per member is always registered to that member.

Hand out and take back

Select tags and Assign them to a teammate, who is shown as the holder. Return to pool clears the holder; the tag stays in the fleet and keeps working.

A registered team tag whose card is deleted does not go dead: the next tap opens the holder’s primary team card. When you remove a member and hand their work to a colleague, the tags that opened the leaver’s card open the colleague’s card from then on.

Views of the fleet

Tab	Shows
All	Every registered tag
Assigned	Tags handed to a teammate
Unassigned	Tags in the pool, not held by anyone
Unclaimed	Pre-encoded tags nobody has claimed yet
Overridable	The tags of event batches, one by one

Above the table, each batch has one summary row: batch name, mode, how many of its tags open a card, taps, and when one was last tapped. Overridable tags are not listed in the main table; their batch row stands for them.

Event batches

The flow for an event with hundreds of tags:

1. Provision an overridable batch.
2. Hand the tags out. Each member taps theirs once and picks their team card. No admin is needed.
3. After the event, Lock batch to freeze who holds what.

While a batch is overridable:

• Any active member of your organization who taps a tag can point it at one of their team cards. Personal cards are never accepted.
• A colleague can re-point a tag a member already took; physical access is the boundary. Lock the batch when that should stop.
• The member who took a tag cannot lock it to themselves. Only an admin locks.
• A prospect who taps a tag sees the card and nothing else.
• Taps count toward the card’s views, not to a per-tag figure in the summary.
• Tags that nobody uses for 400 days are deleted. Registered tags are never deleted automatically.

Lock batch turns every tag into a registered tag that opens the card it was given; only an admin can change it afterwards. Make batch overridable does the reverse and clears the holders. Both are also available per tag from the bulk bar.

Members can also write overridable tags themselves, from their phones: a handover tag (see Write tags to give away) registered against a team card lands in the fleet as an overridable batch named after that card, one batch per member and card. Lock, make overridable and remove work on it like on any provisioned batch.

Remove tags

Remove deletes tags from your fleet, up to 5,000 at a time or a whole batch. Their links stop working for good, so keep it for tags that are lost, misprinted or retired.

This is different from a person removing their own tag, which releases it for the next person. A fleet remove is final.

Taps and analytics

Every tap is a view of the card it opened, so taps appear in card analytics as a breakdown of views. Registered tags carry their own tap count in the fleet table; overridable batches show the total for the batch.

AI assistants

The MCP server offers list-org-devices and assign-device (which can also make a tag overridable or lock it). There is deliberately no tool that provisions, takes or removes tags: a batch mints links that get printed into the physical world, and removing one is final. See MCP server.