Keep articles accurate
Fern keeps published articles true in two ways. Verification checks what your articles say against your product. Audits look for what is missing.
Verification and scheduled audits are included in Pro and Enterprise. On an older plan, check Pricing and plans. Owners and admins run checks, dismiss findings, publish fixes, start audits and change these settings.
Verification
Verification reads each published article and checks its claims against your code, your website and your API reference. It uses support conversations only when none of those is connected. Start a check from Verification with Verify docs, or check one article from the editor with Verify this article.
Articles sort into Needs review, Up to date and Can't verify. Can't verify means no connected source covers the article, a source could not be reached, the article is not on the website you set, or the check did not finish. Connect a source, fix the connection or update your website URL, then check again. A check that did not finish runs again on the next check, or on its own when Continuous verification is on.
For an article in Needs review, choose Draft the fix. Fern rewrites the flagged sentences, and you review the draft and choose Publish changes.
Keep checking on its own
Continuous verification is off until you turn it on in Fern > Customize > Automations. Fern then checks each article again within 30 days of its last check, against your code and site.
What Not an issue does
Not an issue dismisses every open finding on the article. The article moves to Up to date, any fix Fern was drafting for it stops, and Fern does not raise the same claims again on later checks.
If you dismissed something by mistake, choose Undo on the confirmation, or find the article in the Dismissed tab, which shows who dismissed each finding and when. Restore puts the article back in Needs review with its findings, and brings back Fern's drafted fix if nobody has edited the article since. To dismiss one claim and keep the rest, open the article in the editor and dismiss that claim in its verification panel.
Audits
An audit looks for gaps: questions customers ask in support that no article answers, help center searches that found nothing, and recent changes in your code. Its findings land in one audit thread in Fern's list, each with its evidence. Choose Draft with Fern for the ones worth doing and dismiss the rest.
Start an audit any time with Create Audit in Fern's list, on any plan. Scheduled audits run Weekly. Change that to Every 2 weeks, Monthly or Off in Fern > Customize > Automations. They start once you have connected a support tool and Fern has finished reading its history.