Skip to content

Verification

In a company of any size, several tables end up with almost the same name. Verification is how you say which one the organization actually stands behind.

Any table can be verified, Foundation, Integration, Derived, and Dynamic alike, and so can a metric, which is a special kind of table.

State What it means
Unvetted Nobody has endorsed it yet. This is where everything starts.
Verified An admin has endorsed its definition. You can rely on it.
Verified · review pending It was verified, but its definition has changed since. The endorsement is paused, not withdrawn.
Retired No longer the right thing to use. Still live and still queryable, but pushed down in search.
Verifying fingerprint… Transient and rare: the table is verified, but Ronja can’t yet say whether its definition has moved. Shown as Rehashing where space is tight.

Trust is separate from whether a table is finished building: a fully built, live table can still be Unvetted.

Verifying fingerprint… normally clears on the table’s next successful build. If it stays, an admin can click Verify again on the table’s page to re-stamp the endorsement; for a metric, rebuild it first and then verify.

A metric always shows its trust badge, including Unvetted. An ordinary table shows one only when it is Verified, Verified · review pending, Retired, or Verifying fingerprint…, so an unvetted table carries no badge. In Search (⌘K), a result shows a badge only when the table is Verified or Retired; open the table to see the rest.

Open the table, open the Details tab, then expand Table governance to find the Governance · admin only panel.

  1. Click Verify. The table’s definition is fingerprinted at that moment, and the badge turns green.
  2. To step back from an endorsement, click Retire. The table keeps working; it is flagged historical and demoted in search.
  3. A retired table is brought back with Re-open, which returns it to Unvetted.

Verification is never automatic.

An admin can also ask Ronja in a chat: “mark the Orders table as verified”, “retire the old revenue table”, or “that change is fine — acknowledge it”. She makes the change straight away, without an approval step, and reports the table’s new state. She never verifies anything on her own initiative, or for someone who is not an admin.

Some tables cannot be endorsed at all. On those, Verify is greyed out and the panel says why:

  • “This table has to build successfully before it can be verified.” The table has never finished a build.
  • “Move this table into a feature before verifying it.” The table belongs to no feature.
  • “Unarchive this table before verifying it.”
  • “This table is not published to any discovery surface, so there is nothing to endorse yet.”

A table in the trash can’t be verified either; restore it first. In every one of these cases Retire and Re-open still work.

Once a table is verified, Ronja watches its definition and tells you when it moves. What counts as the definition depends on the kind of table:

  • For a Derived table or a metric, it is the calculation, followed all the way down through the tables it is built from. A change to an upstream table’s own SQL drifts everything downstream of it.
  • For a Foundation, Integration, or Dynamic table, there is no calculation to read, so it is the source the table reads from plus the shape it produces — which columns exist and what type they are. Re-pointing a connection, or the upstream system adding, dropping, renaming, or re-typing a column, all count.

Extra rows alone never count: a verified table stays verified through a daily refresh that only adds rows. A column being added, dropped, renamed, or changing type does count, including when the data itself causes it, as when a column that had only been empty receives real values and settles on a type. Treat that as a prompt to look, not as an error.

When the definition moves, the badge changes to amber Verified · review pending and the admins are notified, plus the owner for a metric. The table keeps working. An admin then either clicks Acknowledge (“I have looked at the change and it is still correct”), which restores the clean badge, or has the change reworked.

On a metric’s page, drift shows as one line under the chart: “Definition changed since it was verified — an admin needs to review it.” An admin sees Acknowledge and Request re-verification on that line; everyone else sees the line alone. The Governance · admin only panel sits beside the chart (below it on a narrow screen), under Verification, which says who verified the metric and when; the trust badge beside the metric’s name jumps there. Drift is separate from the review pending banner a reviewer sees on a submitted draft.

A verified table ranks ahead of its rivals and a retired one behind them, with different force in the two places you search.

How well a result matches what you typed comes first: an exact name match wins even if it is retired. Verification decides the order among results that match equally well: the verified one first, the retired one last, each with its badge. Nothing is hidden, and a retired table you search for by name still comes back.

When Ronja looks for a table herself during a chat, verification adjusts how relevant she judges each result, alongside how recently its data was refreshed. A verified table is scored up, a verified metric furthest of all, and a retired one down. A verified table can be offered ahead of one whose name matches your words more closely, and a retired table can drop off the list she looks at entirely.

To use a specific retired table in a chat, name it directly, or open it from Search (⌘K), which never drops it. When Ronja uses a verified table or metric, she says so.

  • It does not say the data is right. Verification is about a table’s definition. Whether the rows in it are still what they should be is what health checks answer — a verified table can carry a failing check, and both badges are worth reading.
  • It does not restrict access. Verification says whether a table is trusted, not who may read it. Access is decided by scopes and sharing.
  • It does not survive a move. Moving a table into another feature returns it to Unvetted.

Verification is also separate from drafts and approvals: a draft is a change waiting to land, while verification is a statement about what has already landed.