The privacy boundary in the Member Directory

The Member Directory is where an association HQ manages its own roster and reviews members asking to be recognized on Verinode. It looks like a simple admin screen, but it is built around one hard rule: everything on this page is either data your association already owns (the roster you imported) or data an operator handed you directly when they filed a claim (a member number, an email, a company name). Verinode HQ never reads into an operator's business data to populate or verify this page, and it never will. This article explains what every element on the page shows, where that data comes from, and why the boundary is drawn where it is.

Where to find it

HQ sidebar → Membership → Member Directory (hq.verinode.ai/members). It appears for association HQs under the Membership section of the sidebar, alongside Growth & Retention. It is not visible to franchise or enterprise HQs, this page is specific to associations that run a paid-member roster (dues, renewals, member numbers), not to franchise networks tracking their own locations.

The four stats at the top

The page opens with four tiles:

• Members, the total count of rows on your imported roster. Shows "Import your roster to begin" until you upload one, then reads "On the roster."
• Dues Current, the percentage of your roster whose dues status is marked current, with the raw count underneath (e.g. "42 of 58 current").
• On Platform, the percentage of your roster that has been matched to a verified Verinode operator account, with the raw count underneath (e.g. "19 verified on Verinode").
• Pending Review, the number of self-declared claims from operators waiting for your decision. Reads "Queue is clear" at zero, or "Awaiting your verification" once there is a queue.

All four numbers are computed from your own roster and your own claims queue, nothing here reaches into an operator's job, financial, or client data.

Import Roster

This is how your roster gets into Verinode in the first place. You upload a CSV with these columns: member number, company name, contact email, city, state, dues status, renewal date. Re-importing updates existing rows by member number, so refreshing dues status or renewal dates each cycle is a normal, repeatable action rather than a one-time setup step.

This roster is entirely association-owned data. Verinode does not generate it, infer it, or supplement it from any other source. What you upload is what shows on the page.

Next to the upload control is a Reconcile dues button. Use it any time you want to manually re-run the dues check outside of an import (for example, right after you've hand-corrected a member's status in the CSV and re-uploaded). It reports how many members were activated and how many were revoked as a result.

Verification Queue

This is the heart of the privacy boundary, and the reason the page exists as an admin review step rather than an automatic sign-up.

Here is the sequence that produces a row in this queue:

1. 1An operator self-declares. From their own settings, an operator can state "I am a member of this association" and optionally enter the member number they believe is theirs. Verinode records this as a pending claim tied to their account. Nothing is activated yet, no benchmark cohort, no badge.
2. 2You import your roster. Your CSV becomes the authoritative source of who is actually a paying member, at what dues status.
3. 3Verinode proposes a match. For every pending claim, Verinode compares the member number or email the operator entered against your roster and surfaces a candidate row when it finds a strong match, either a member-number match or an email match. This is a suggestion only. It never activates anything on its own.
4. 4You approve or reject. You, the association admin, make the final call.

Each row in the queue shows:

• The company name from the matched roster row.
• The match type, "Member number match" or "Email match", telling you which field lined up.
• The roster member number, if one exists, shown as #12345.
• A note reading "dues not current" if the roster row's dues aren't current, since that blocks approval.

Two actions are available per row:

• Approve, confirms the match. This activates the operator's association membership (which turns on their benchmark cohort) and grants their member badge. Approve is only enabled when the matched roster row's dues are current; if dues have lapsed, you'll need to resolve that on the roster side first.
• Reject, declines the match. The claim is marked rejected and drops out of the queue.

When the queue is empty, the page reads: "No members are waiting for verification. New requests appear here as operators declare membership."

This is the entire privacy boundary in practice. The fields you see on a queue row (company name, member number, dues status, match type) are either your own roster data or the claim identifiers the operator entered themselves when they asked to be verified. Verinode HQ has no path into the operator's actual business: no job data, no financials, no client list, no vendor relationships. Matching runs on identifiers alone, and even a strong match is never auto-approved. Approval is always a manual decision by an association admin.

Roster

Below the queue is your full member list, one row per roster entry:

• Company name, with an "On Verinode" tag appended when that member has been matched to a verified operator account.
• Underneath: the member number (as #12345) and city, state, separated by a middot. If there's no member number on file, this line reads "No member number."
• On the right: the dues status label, "Dues current," "Lapsed," "In grace," or "Unknown", colored to match the signal (green for current, red for lapsed, yellow for grace, muted gray for unknown).
• Below that, if a renewal date is on file: "Renews [date]."

When the roster is empty, the page reads: "Your roster is empty. Import a CSV above and members will appear here."

Why the boundary is drawn here

Verinode HQ's entire value is trustworthy network intelligence: aggregates, rankings, and compliance status across your membership, never a single operator's private business data. The Member Directory is the one place where HQ handles identifying information at all, and it's scoped as narrowly as the workflow allows: your own roster, plus the identifiers an operator volunteers when asking to be recognized as a member. That is enough to answer the only question this page needs to answer, is this claim really this roster row?, without ever opening a door into what that operator's business actually looks like day to day. Membership approval activates a benchmark cohort membership, not a data-sharing relationship; franchisees and association members remain memberships on Verinode, never seats with broader visibility into their business granted to HQ.

Related help

• /help/hq-membership-growth-retention
• /help/hq-privacy-aggregates-only
• /help/hq-benchmark-cohorts