You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Publisher creates an entry and assigns an Editor as author
Editor goes in, edits the entry, saves as Draft as many times as needed, clicks Submit for review when ready
Publisher clicks the entry pending for approval, reviews content, enables the entry, clicks Publish Draft
Pitfalls:
in step 2, Editor can create as many drafts as wanted, and Submit all of them for review => Publisher may be confused as to which one is to go live.
in step 2, Editor clicks Submit for review without clicking Save as Draft, and disregards the warning popup => new content is lost, and Publisher gets notified to review an entry that did not change.
in step 2, Editor doesn't Submit for review => Publisher is unaware that there is a new version, Editor can create new Drafts, nothing changes live
in step 3, Publisher approves the draft directly without clicking the entry => the entry remains a Draft, Editor may edit the Draft again and create new Drafts, no changes live.
in step 3, Publisher enables the draft and saves the Draft => Editor cannot edit their Draft, can create new Drafts, no changes live.
in step 3, Publisher clicks Publish Draft directly without enabling it => Editor can create new Draft, can freely edit the actual entry without creating a new Draft, and the entry page gives a 404 not found ; when the Publisher notices the 404 not found and wants to enable the entry, then entry content may have been changed by Editor and needs to be reviewed again before being enabled.
The text was updated successfully, but these errors were encountered:
froger-me
changed the title
How to make an Editors able to edit only one entry, and limit pitfalls?
How to make Editors able to edit only one entry, and limit pitfalls?
Oct 20, 2016
Use case:
Editors and Publisher are not tech-savvy people.
For a given section, permissions:
Journey:
Pitfalls:
The text was updated successfully, but these errors were encountered: