The discussion revolves around implementing “guard-rails” for categories with only scheduled posts. mattdm describes a setup with an “Announcements” category and a “Draft Announcements” category, where certain users can schedule posts but should not post directly to the announcements category. The issue is that users with permission to schedule posts can still accidentally post directly to the announcements category. Jagster suggests setting suitable rights for groups to post and read in each category, but notes that scheduling is currently only allowed for staff/TL4 via the topic timer, with no option to change this. mattdm clarifies that they can set up the initial categories and permissions, but still need a solution to prevent accidental direct posting to the announcements category.
an “Announcements” category which people should not post in accidentally
a “Draft Announcements” category which anyone signed in can post to
some set of people who can choose to Schedule Publishing for those posts[1]
Problem
I assume that in order to schedule publishing to a category, one must have permission to post in that category.[2] But, I don’t want people to post directly. I want the Scheduled Publishing workflow to be required.
I don’t need it to be absolutely blocked, because I assume everyone at that level has good intent. How can I keep it from happening accidentally?
First two are trivial and needs only suitable rights which group can post and read. Like posting on Announcement is allowed only to staff, but everyone can read. And Draft — allowed only for TL0 for example.
Scheduling is allowed only to admins staff/TL4 via topic timer and that can’t be changed. But here is already at least one request for that option, if I’m remembering right.
Oh, sorry! I see I wasn’t clear. Those three points are the setup. I can do all of those things, although as you note I would love for the third to be more flexible. The second part is the problem, but let me reword it to be more clear.