We currently do not allow journalist access to WebSked, but we do like using collections for various purposes. In order for a journalist to pitch to a collection they need full Websked permissions. There are no fine grain permission for Websked in the permissions app.
It would be great to allow users to pitch to collections without having to give them full websked access as well as being able to fine tune websked permissions via the app.
Guest
Hi Stuart,
That doesn't really solve for this specific issue, but again, it's not as big an issue today as it was in 2020. However, I'm fully in support of restricting Website A-only users from seeing any Website B content anywhere.
- Brian
Hi Brian,
Would it help to control the content by website? For example:
A user who only has rights to Website A would only see content from Website A on the Stories tab and no content from Website B.
Same goes for pitching content to Publications/Platforms/Collections: if you don't have rights to any of the websites that the Collection is circulated to, then I can't view it or add content to it.
Would that give you the control you're looking for?
- Stuart
Thanks for following up. This workflow is much improved since May 2020 when this idea was first presented. However, in the new workflow, adding Websked app permissions (with no granular Websked permissions granted) still presents a Websked tile to the user, and read-only access to pages and templates, not an ideal user experience.
Hello!
Thank you for your idea and please excuse the long delay in responding.
I'd like to learn more about the permissions you are interested in. A journalist can pitch an article to a Collection from Composer with today's permission settings. What additional restrictions would you want to see in WebSked so you could give your journalist just the permissions they need?
Thanks!
Stuart
Sr. Product Manager for WebSked