As a site admin I want to be able to control who has access to Collections in Websked, so that only those users I approve can alter the parts of pages on our website which are controlled by Collections.
I regret to report that Collections permissions are not on the roadmap for the next few months. The team made some progress implementing permissions but shifting priorities has this on the backburner at the moment.
Justinian Hatfield
These are our uses cases:
Only admins should be able to create, rename and change the settings of a collection.
Editors should be able to add/remove/change order/pin stories within a collection, and publish.
Anyone should be able to pitch to a collection from Composer.
Hi all,
I am researching what permissions make sense for WebSked. What kind of use cases do you have for controlling permissions around Collections?
I am aware of these:
Only users with XYZ permission can create or edit a Collection
Only users with ABC permission can add, pin, reorder, or move content within a Collection
What else?
Stuart
Sr. Product Manager for WebSked
Hi Bonnie
I regret to report that Collections permissions are not on the roadmap for the next few months. The team made some progress implementing permissions but shifting priorities has this on the backburner at the moment.
Hi Ryan, wondering any news you can bring us on this idea?
Good news! Thanks!
We will add more granular permissions to WebSked later this year.
Thanks for the Ideas!
Ryan