Why a draft waits for a person, by default
A church speaks in one voice. Folio drafts notes and answers, and by default a person signs off before anything reaches members.
6 October 2026
A sermon is a church saying what it believes, out loud, to the people it is responsible for. When that teaching is turned into a note, an answer, or a verse on a screen, the church is still the one speaking.
That is why Folio does not publish on its own. It drafts. A pastor, a media lead, or a member of staff reads the draft, checks the scripture, and approves it. Until that happens the draft stays private, and members and public links never see it. A church can opt in to automatic approval for notes that pass the checks; it is off by default, and a shared page says which kind of approval applied.
A draft, not a decree
The first draft is a starting point. It carries your church’s structure and voice, and it cites the moment in the sermon each claim came from. Staff can edit it, request changes, or throw it out. The approved version is the one that speaks for the church, and it stays intact while the next draft is improved.
What the gate protects
- Members and public links never see a draft.
- Every answer and note points back to the teaching it came from.
- When the church now teaches something differently, readers are pointed to the newer teaching.
- Your church’s private teaching and drafts are used to serve your church, not to train public models.
The gate is the heart of the product. Everything else, the library, Ask, the notes, the booth on Sunday, is built on top of it.
One exception is a choice a church makes for itself. An owner can turn on automatic approval for notes that pass guardrails: enough source material, scripture that checks out, and no duplicate. It is off by default, and any note that fails a check goes to a person.