# Knowledge health: see which documents need attention

The Knowledge health page shows how your documents are holding up and lists the ones to look at first, with what is wrong with each and how to fix it.

GPTree keeps a record of where every answer came from. Knowledge health turns that record around: instead of asking which documents an answer used, it asks which of your documents need attention because answers rest on them.

## Opening it

On a computer, open the Knowledge page and choose Knowledge health in the panel on the left, below Where your knowledge reaches. A phone does not show that panel. The page is for workspace owners and admins. If you are a member of a workspace but not an owner or admin, the page tells you so and shows nothing else.

If you look after more than one library, for example your own and your workspace's company library, a Library menu at the top lets you see all of them together or one at a time.

The numbers are counted once a day. The page says when they were last counted, and before the first count it says the first one runs overnight.

## The six numbers at the top

Choose any of them to see the rows behind it.

- **Coverage**: how many of your documents GPTree can search and quote, and how many uploads could not be read at all. A document is searchable once its text has been split into passages. Uploads that could not be read are listed on the Knowledge page with the reason.
- **Freshness**: when a new version last arrived, for each kind of source, and when each connected source last synced.
- **Contradicted claims**: claims in Knowledge API answers from the last 90 days that verification found contradicted, counted against the document the answer cited. There is no open or closed state for a contradiction yet, so this is a count over the window.
- **Unreviewed facts**: facts GPTree pulled out of your documents that are still waiting for a person to check them. Each document links to its project's Review tab.
- **Connector failures**: connected drives and databases that stopped syncing, because they need reconnecting or their last sync failed. Each has a Reconnect link. The page never shows a connection's error text or credentials.
- **Unanswered questions**: your Knowledge API questions from the last 30 days whose answer was refused or stated low confidence. These show what people needed that your documents could not supply. You see the questions and a count, never who asked. Chat answers are not counted here, because only the Knowledge API keeps this record.

## Answers whose sources changed

Two more numbers appear once GPTree checks answers against document changes:

- **Possibly stale answers**: answers you can open that quoted a document in these libraries which has changed since, with what happened to each passage, and how many answers are still being checked for changes. It says what happened to the supporting passage, not that an answer was mistaken. See [Answers that may be out of date](/learn/answers-that-may-be-out-of-date).
- **Impact checks**: how far behind those checks are, and when the checker last ran. It shows an age, never a count of anyone's answers.

These are worked out live for you, not once a day. In the ranked list below, a document's entry then also says how many answers resting on it may be out of date and how many are being checked.

## Documents to look at first

Below the numbers is a ranked list. A document ranks higher the more is wrong with it (contradicted claims and facts waiting for review), the more answers rest on it, and the longer it has gone without a new version or a review. A document nothing has cited does not appear, however much is wrong with it, because no answer depends on it yet. A document changed today still appears if answers rest on it and something is wrong.

Each entry spells out its parts, for example "3 contradictions, 2 facts to review, cited by 82 answers, last changed 730 days ago", and offers the fixes that apply:

- **Review** opens the facts waiting for review.
- **Supersede** opens the project's Files tab, where you can mark a newer document as the one to use.
- **Reconnect** appears when the document comes from a connected drive that has stopped syncing.

For a document that is not in a project, Review and Supersede open the Knowledge page.

The ranking is a first version and will be tuned as people use it.

## What you see depends on what you can open

Being an owner or admin lets you see the document numbers for the libraries you look after: coverage, freshness, connections and facts waiting for review. It does not let you see anyone else's answers. Every number that comes from answers counts only answers you could open yourself: conversations you can open, crew runs of crews you own, and your own Knowledge API answers. Anything else is left out without a trace, not shown as "others". Two admins looking at the same library can therefore see different answer counts.

If you lose access to a conversation, it stops counting toward your numbers the next time they are worked out, which is at most a few minutes later.
