Plan requirement
| Subscription | Suite Enterprise or higher, Knowledge Enterprise |
| Access | Agent |
Team Publishing adds states and ownership to articles, so a knowledge base can be maintained by more than one person.
What it adds
- States beyond draft and published: in progress, awaiting review, ready to publish.
- Assignment, so an article belongs to somebody. You can leave an internal note with it, which is where the reason for the assignment belongs.
- Review before publishing.
- Work in progress on an already published article, so an update can be prepared without changing what readers see.
- Scheduling. An article that is ready to publish can wait for you or go out automatically at a time you set.
Archived sits alongside these: an article that has been unpublished and moved out of the way rather than deleted. It is the honest end for something that is no longer true but that somebody may still ask about.
Scheduling is the one to set up early. A price change, a new opening time, a product going on sale: the article can be written, reviewed and approved this week and appear on its own on the day it becomes true.
The problem it solves
Without it, an article is either invisible or live, and nothing says whether a draft is abandoned or nearly finished. With two writers that is manageable; with six it is not.
The state that matters most is work in progress on a published article. Without it, any substantial rewrite is live from the first save.
Review is a habit, not a feature
Team Publishing makes review possible. Whether it happens depends on somebody being responsible for it and having time.
A review queue nobody works through is worse than no review, because writers wait instead of publishing.
Start light
Turning it on does not force review. Using the states for visibility, and reviewing only what genuinely warrants it, is a reasonable first step.
Comments
0 comments
Article is closed for comments.