What publishing does
Publishing turns your integrity report into a certificate: a public verify link (usefolio.co/verify/<code>) that anyone can open to confirm you wrote the document. The link stays live and its code never changes; editing it later doesn't create a new one.
You publish from the Certificate tab of the Manuscript integrity report in the editor. Certificates are free on every plan: 3 a month on Scholar, unlimited on Fellow and Chair.
Choosing what a professor's check can see
Before you publish, you choose what shows up if a professor ever runs a detailed check on your document. The public summary (word count, citation count, total AI use) always shows. These three only add detail on top of that, and only if you turn them on:
- Revision timeline: when your draft grew, across sessions.
- Paste activity: how much text was pasted in (a count only, never the pasted text itself).
- AI-assist detail: which Folio AI features you used, broken down.
Leaving all three off doesn't hide the certificate. It just keeps the public summary as the only thing a check can surface.
Next to the AI-assist detail switch, the report shows you that exact breakdown before you decide: which Folio AI features you used, grouped by section, with a running total of AI actions logged on the document. It's your own record either way; the switch only decides whether a reader of your published certificate sees it too. The public total is shown regardless of how you set it.
Show the document itself is different: it puts the document's current text on the verify page, and a page with the text on it is also one search engines and AI assistants are allowed to find and list. It starts off, and turning it off again takes the page back out of Folio's sitemap and tells search engines to stop indexing it. Two more options need that page to be public:
- Tag as Preprint adds a stable citation permalink readers can copy, and lists the work among Folio Preprints.
- State the outcome lets you say what you found. It's optional, and a null result is worth stating too.
Changing your mind after publishing
Once a certificate is live, the Certificate tab shows its verify link and the same switches. Change them and choose Edit sharing to save. This re-publishes the certificate, but the link and its code stay exactly the same; only what a professor's check tool is allowed to show updates. Editing sharing settings never costs a publish credit, on any plan: it's managing privacy on an attestation you already made, not creating a new one.
Filing a correction
Caught an error of your own after publishing? File a correction records where it was, what it said, what it says now and why, with a timestamp, and shows it on your certificate. It's a voluntary record that you fixed your own mistake, not a retraction.
Revoking a certificate
Revoke certificate takes the certificate down immediately. Anyone who opens the link from then on sees a Certificate revoked notice with the date it was revoked, instead of the certificate itself. Revoking doesn't touch your integrity report or your document, and it doesn't cost a credit either.
You can publish again whenever you want after revoking. That brings back the same public verify link, not a fresh one, as a valid, freshly issued certificate, and lets you pick your sharing choices again from scratch. Because that link had been taken down on purpose, Folio checks with you first: you'll see a prompt confirming the same link is about to go live again, and you have to choose Publish anyway before it does. Unlike editing sharing settings, bringing a certificate back after a revoke is a real publish, so on Scholar it counts against the monthly allowance.