You should not have to email anybody to fix a typo.

A name is spelled wrong in Sunday's message.

A transcript hears a name it has never met and guesses. It is almost always a name, and it is almost always somebody who will notice.

You open the message, change it, save. There is no queue, no ticket and nobody to email. Once you have edited something, your version is kept: it does not get written over later.

If the same name keeps coming out wrong week after week, that is worth telling us, because that one we can fix at the source.

Somebody said something from the stage that should not live on a public page forever.

A name in a prayer. A diagnosis. A testimony that was meant for the room. Fine in front of two hundred people, permanent on a page a search engine reads.

The transcript can be turned off for that one message without touching anything else, or edited before it publishes. You can also turn transcripts off across the whole site if that is the call your church wants to make.

The recap, the passages and the page all stay. Just not the word-for-word.

Your youth pastor should be able to fix message pages but not see billing.

Most systems solve this by giving everyone the same login and hoping. Then somebody leaves and the password does not change, because changing it means telling nine people.

There are three roles and they are what they sound like. An owner has everything, including billing and the connection to your recordings. An editor can fix and publish message pages and nothing else. Care gets the prayer requests by email and sees nothing else at all.

You invite people and you remove them, from your own admin, without asking us.

You want to read everything before it goes live, at least for a while.

There is a switch. Set it to review and nothing publishes until somebody there says so, and what is waiting sits at the top of your admin so nobody has to hunt for it.

Most churches run on review for a month, see that the recaps read the way they want, and then switch to automatic. Some never do, and that is a perfectly good way to run it.