Do seats belong to a specific client?

No. You buy one pool for the agency — 250 seats on the Agency plan. Allocate 40 to one client and 15 to another, and move them later. Creating a client uses zero seats; seats are consumed only when people actually join.

Can one client see another client's people or contacts?

No. Client workspaces are sealed from each other. A user in one client cannot see another client's members, cards or contacts.

Can the agency read a client's contacts?

No — and this is deliberate. Leads captured by a client's cards live in that client's workspace. The agency console shows counts, never records.

Why was my domain rejected?

Use a subdomain such as cards.yourclient.com, not a bare domain like yourclient.com. Verification uses a CNAME record and a bare (apex) domain cannot carry one, so it could never verify.

How many custom domains can an agency have?

A fair-use ceiling of 50 across the agency — your own domain plus one per client. Email support@nexalink.co if you genuinely need more.

What is the difference between a Member and an Admin?

A Member gets their own white-labeled card. An Admin gets that plus the ability to run their own workspace — inviting and removing their users and managing their branding — without ever seeing your other clients or the agency console.

NexaLink Agency — Admin Guide

How to run multiple clients from one NexaLink account: your own brand and domain, a shared seat pool, per-client branding and domains, and a client Admin who runs their own workspace.

Setting up for the first time? Start with Getting Started — the same material in the order you actually need it, from an empty account to your first client live on their own domain. This page is the reference to come back to.

1. How it fits together

Your agency                     ← your brand, your domain
└── Seat pool: 250 shared seats
    ├── Client A                ← own users · branding · domain
    │     ├── admin@clienta.com   ADMIN   ← runs their workspace
    │     └── sam@clienta.com     MEMBER  ← just gets a card
    └── Client B
          └── admin@clientb.com   ADMIN

Three things follow from this, and they are the whole point:

Seats are pooled, not per client. You bought seats for the agency, not licences per client. Move them as your book changes.
Clients are sealed off from each other. A user in one client cannot see another client’s people, cards or contacts.
You see counts, never contact records. Leads captured by a client’s cards stay in that client’s workspace. This is what makes the model safe to sell to your clients.

2. Set up your agency

Name your agency — Settings → Agency name. This is the white-label name shown in the console, not “NexaLink”.
Bind your own domain — Settings → Your agency domain, e.g. cards.youragency.com. This serves your cards on your domain, so a prospect never sees nexalink.co.

Use a subdomain (cards.youragency.com), not a bare domain (youragency.com). Verification uses a CNAME record, which a bare domain cannot carry.

3. Create a client workspace

Agency → + Add client. Give it a name and the number of seats to allocate from your pool. Creating a client uses zero seats — they’re consumed only when people join.

4. Brand the client

Open the client → Branding. Set company, logo, primary colour and website. Tick “Lock these on every card in this client” and those values are pushed onto every card in the workspace, so the client looks consistent and members can’t drift off-brand. The preview beside the form shows the result before you commit.

5. Give the client their domain

Open the client → Domain → enter cards.theirdomain.com → Bind. Hand this record to whoever runs their DNS:

Type   CNAME
Name   cards.theirdomain.com
Value  cname.vercel-dns.com

Once published, click Verify DNS — the status moves from Pending DNS to Live. One domain per client, and it serves that client’s cards, never yours.

6. Add their people — and hand the client off

Open the client → Users → enter an email → choose a role → Invite.

Role	What they can do
Member	Their own premium, white-labeled card. No admin surface.
Admin	All of the above, plus runs their own workspace: invites and removes their users, manages their branding.

This is how you hand a client off. Invite their lead contact as Admin and they self-serve from then on. They sign in normally, see Team in their rail (not Agency), and manage only their own workspace — never your other clients, your seat pool, or the console.

7. Day to day

Dashboard — clients, seats, domains, and anything needing attention (failed DNS, a client with nobody invited, an exhausted pool).
Clients — searchable list with domain, seats and status.
Seats — pool usage and each client’s allocation.
Domains — every client domain and its status in one place.
Analytics — across all clients: seated users, cards live, card views, and contact counts.
Agency team — who administers the agency, and everyone seated across your clients.

8. What white-label covers

White-label applies to the web experience, which is what your clients’ prospects actually see:

Their cards on your client’s own domain, with no NexaLink branding
Your agency name and logo throughout the console
Invite emails from your own verified domain

The mobile apps are not white-labeled. Your clients download NexaLink from the App Store or Play Store and sign in there — the app carries our name and icon. If your clients only ever share their card link or QR code, they and their prospects stay entirely within your brand. The app is optional, and mainly useful for scanning cards on the move.

9. What isn’t built yet

Stated plainly so nothing is a surprise:

The console on your own domain. Your cards are on your domain today; your clients still sign in at nexalink.co.
White-labeled mobile apps. See above — the apps stay NexaLink-branded.
Extra agency admins. You are the sole agency administrator; colleagues who co-manage specific clients are planned.
A shared template library. Branding is set per client today.
Billing. Nothing to manage — the Agency licence is lifetime. Pool expansions are handled by us directly.

10. Troubleshooting

What you see	What to do
“Use a subdomain…”	You entered a bare domain. Put `cards.` in front.
Stuck on Pending DNS	The CNAME isn’t published or hasn’t propagated. Check with `dig cards.theirdomain.com CNAME`; propagation can take a few hours.
“Already in use on another account”	It’s on a different NexaLink account. Email support and we’ll sort the transfer.
“Fair-use ceiling”	50 domains across the agency. Email support to raise it.
An invite fails mentioning the pool	You’re out of seats. Reclaim from a client that isn’t using its allocation.
A client admin can’t see their workspace	Check they were invited as Admin (not Member) and have accepted the invite.

Questions

Email support@nexalink.co — include the client name, and for a domain issue the exact domain.

← All guides · Agency plan overview