Verinode
Open Verinode

The Location Directory and member lifecycle

The Location Directory is the single roster table behind your network: one row per location, whatever your network calls them (franchisees, locations, or members), tracked through three states as t…

9 min read·Updated July 14, 2026
On this page

What the Location Directory is

The Location Directory is the single roster table behind your network: one row per location, whatever your network calls them (franchisees, locations, or members), tracked through three states as they come onto the platform. It is where an HQ admin adds a location before its owner has ever logged in, edits that location's basic profile fields, and removes a placeholder row if it was added by mistake or the deal fell through.

This is administrative roster data, not a franchisee's private business data. Verinode HQ never sees a member's jobs, invoices, margin, or day-to-day records, those stay inside that member's own Verinode IQ account. The Location Directory only ever holds the profile fields your network's own admin team enters: a location name, a city and state, a contact email, and (once set) who opened it and which owner group it rolls up under. Nothing in this table is derived from a member's performance data, so it is not gated by the anonymization rule that governs the rest of the Network Health page. See the section on privacy below for exactly where that line sits.

Where to find it

Open Network from the HQ sidebar (the label reads Franchisees, Locations, or Network depending on how your network is set up) to land on hq.verinode.ai/network, HQ's Network Health home. Scroll to the Explore row near the bottom of the page and click the Location Directory tile. Its value is the total count of locations on your roster, and its preview shows the Active, Invited, and Pre-loaded split as colored segments. Clicking it opens the network-health slider on the Location Directory tab, which is the table this article covers.

Note

The Explore row has other tiles that also touch this same roster (Active, Invited, Seeded, Cert Watch, Interventions), but those open a different overlay: a read-only roster slider where each row with a linked owner account drills into that member's full profile card. The Location Directory tab covered here is the one place with the admin controls: add, edit, and remove a pre-loaded row. Both surfaces read the same underlying roster, so a change you make in one appears in the other after the page refreshes.

The three-state member lifecycle

Every location in the directory sits in exactly one of three states, shown as a status badge:

  • Pre-loaded: HQ added this location to the roster before its owner ever signed up. It is a placeholder record, a name and a way to contact the location, with no linked operator account yet.
  • Invited: an invitation has gone out to the location's contact email. The record still has no linked operator account.
  • Active: the location's owner has signed up at app.verinode.ai and linked their operator account to your network. From this point on, their aggregated rollups (margin position, compliance, benchmarks) start flowing into the rest of Network Health.

The section description at the top of the table spells out the common path in plain terms: "Seed franchisee locations before they sign up. New rows start as Pre-loaded and turn active once the owner links their operator account." In practice, most rows move straight from Pre-loaded to Active the moment the owner signs up and connects their account, since it is the sign-up and account link that flips the status, not a step you take inside this table. Invited is a real, distinct status you will see on rows once your network's invite step has reached out to a location's contact email; it is not a status you set from the Edit form here, since editing a row only changes its profile fields, never its lifecycle state.

The directory table

The table lists one row per location, sorted by status then alphabetically by name, with these columns:

  • Location: the location's display name (for example "Atlanta North").
  • City and State: the location's address fields. Either shows a dash when not on file.
  • Status: the Pre-loaded, Invited, or Active badge described above.
  • A fifth, unlabeled column holding the Edit and Remove controls. It only appears for admins; see below.

Compliance percentages, program adoption counts, and open-intervention flags are not shown in this table. Those live on the Cert Watch tile, the Interventions tab, and a member's own profile card elsewhere on Network Health, once a location is Active and generating rollups.

Adding a location (admin)

Admins see an Add Location button in the top-right of the section header. Clicking it opens the Add Location form:

  1. 1Location Name (required): a short, recognizable name, for example "Atlanta North."
  2. 2City and State: optional. State auto-uppercases as you type and is capped at two characters, so it reads as a postal abbreviation (for example "GA").
  3. 3Contact Email: optional at this stage. It is the email your network's invite step will later use to reach this location, and it is encrypted at rest under your network's own shared key.
  4. 4Click Add Location to save.

The form reminds you underneath the fields: "New locations start as Pre-loaded. The owner becomes active once they sign up at app.verinode.ai and link their operator account to this network." Save without a Location Name and the form blocks you with "Location name is required." A name that already exists on your roster is blocked with "A location with that name already exists," since names have to stay unique inside one network. A successful save shows a confirmation toast reading "Location added" and the new row appears in the table, filed under Pre-loaded.

Editing a location (admin)

Click Edit on any row to open the Edit Location form. It carries every Add-form field plus two that only exist here, since a brand-new row has no history for them yet:

  • Location Name, City, State: the same profile fields as Add, this time pre-filled and editable at any lifecycle stage.
  • Contact Email: pre-filled if set. The form notes it is "Used for the invite when this location is promoted from seeded to invited."
  • Opened: a date field for when the location opened. The form explains why it matters: "A young location below the network median reads as ramping, not failing." Recording tenure keeps a newer location's numbers from being misread against a network median built mostly from established locations.
  • Owner: a free-text name for the location's owning group, for grouping multi-unit owners. The form explains: "Locations with the same owner roll up together, so a multi-unit owner is one view." Locations sharing the same owner name are keyed together automatically behind the scenes, so entering the same owner text on two locations is enough to roll them up as one owner.

Save with a blank Location Name and the form blocks you with "Location name is required." (shown inline, not as a toast). A successful save shows "Location updated" and the row reflects the change immediately.

Removing a location (admin): the seeded-only rule

Remove only appears on rows whose status is Pre-loaded. Once a location is Invited or Active, there is a real (or soon-to-be-real) owner account associated with it, so the row can no longer be deleted from this table. The text under the table for admins spells this out directly: only seeded locations (not yet invited) can be removed, and after an operator joins, their data is preserved: reach out to Verinode support to deactivate an active location instead of trying to delete the row.

Clicking Remove opens a confirmation: "Remove [location name] from the network directory?" with the warning "Only seeded locations can be removed. This action cannot be undone." Confirming shows a "Location removed" toast and the row disappears from the table. If a row's status changed to Invited or Active in the moment between opening the table and clicking Remove, the action is blocked server-side with the same seeded-only explanation, so a stale view can never delete a location that already has operator data linked to it.

The read-only view for non-admins

Everyone else on your network's account sees the exact same table, minus the admin controls. There is no Add Location button, and the fifth column with Edit and Remove is not rendered at all, so the table reads as four columns: Location, City, State, Status. Every row, every name, every status badge is identical to what an admin sees; the only difference is that a non-admin cannot add, edit, or remove anything from this view. This is enforced twice: the button and column simply do not render for a non-admin, and the underlying add, edit, and remove actions independently check the caller's role and refuse the change even if attempted directly.

Privacy: what this table shows, and why

The rest of Network Health (Top Quartile, Watchlist, the Active, Invited, Seeded, Cert Watch, and Interventions roster views, any per-member drill-down) follows a strict rule: in a franchise or association network run as independent operators, a member's name, city, and state are anonymized to a stable label like "Franchisee #XXXX" so that a performance number never gets tied back to an identifiable business. Single-owner, multi-location networks operating as one entity see real names throughout, because it is genuinely one business looking at its own locations.

The Location Directory table you manage here is different, and deliberately so: it always shows the real location name, city, state, and status, regardless of how your network is configured. That is because this table holds the roster information your own admin team entered, the same kind of information a franchise agreement or a membership list already contains, not a member's operating results. Nothing about margin, compliance percentage, benchmark standing, or program adoption appears in this table. Once a location goes Active and starts generating rollups, its performance data feeds the rest of Network Health under whichever privacy rule your network is configured for; the row you manage right here never changes.

Empty and loading states

While the table is loading, it reads "Loading…" in place of rows. If your roster has no locations at all yet, admin and non-admin views alike show: "Locations will appear here as you add them."

How to use it

  1. 1Open Network from the sidebar, then the Location Directory tile in the Explore row.
  2. 2Add every location you already have a relationship with, even ones that have not signed up yet. A Pre-loaded row costs nothing and lets you track who is expected to come online.
  3. 3Keep City, State, and Contact Email current as you learn them, they carry into the location's profile once it goes Active.
  4. 4Fill in Opened and Owner on Edit as soon as you know them. Opened keeps a new location's numbers from reading as underperformance elsewhere on Network Health; Owner rolls multi-unit locations up together.
  5. 5Only remove a row while it is still Pre-loaded. Once a location is Invited or Active, treat the record as permanent and contact Verinode support for anything beyond a profile edit.

Tip

If you are trying to understand why a location's margin, compliance, or benchmark numbers are not showing up anywhere else on Network Health, check its status here first. Everything else on the page only reflects locations that have reached Active.

Heads up

Adding a location here does not send it an invitation and does not create an account. It only reserves a named row on your roster. The location becomes Active on its own, the moment its owner signs up at app.verinode.ai and links their operator account to your network.

Related help

Was this helpful?