We are posting this request after having received reply from Joanne Debo (Arc trainer) that there would be no way at this moment to set level of privacy / restrict content from being shown in WebSked. Even with Distributors/Restrictions configuration in Global settings, the content would still appear in WebSked for all those with access to the tool (but it will be successsfully hidden in Composer if the story gets saved with a target website where other users do not have access to as defined by Squads in Permission).
To further your understanding why this feature is required, I’m giving you an example. Here in our organization (Chosun) we have editorial room where their contents (stories) need to remain private and be published only when its gone through internal review. Often times the stories they manage to create may contain sensitive info which should not be shared even within the organization or a scoop that requires protection from being leaked out to competitors.
As Arc doesn’t provide its own means to hide or restrict stories from being shown to different users, we were suggested from Joanne to create a fake-site in the platform as a workaround and set Squads (associating the squad with that specific fake-site). Lets assume we created a squad named ‘politics_only’ and this squad is linked with a fake-site called ‘politics_only’ and our main site ‘Chosun’ at the same time. Now when a user underneath the squad ‘politics_only’ composes, saves a story in Arc, the user should set primary website (target) to the fake-site ‘politics_only’. In this case, the story will not be shown to different users who does not belong to the ‘politics_only’ squad.
However, this restriction is successful only within Composer. If a user from different squad goes into Websked, that user will still be able to see the story created/saved by ‘politics_only’ user. This is why we’ve been raising this feature where users may manage their contents to be private and appear only once the author decides its ready.
Please review this feature as this is widely requested when we’ve received feedback from our super-user training.
Doma Bang
This is similar to https://ideas.arcxp.com/ideas/WS-I-303, which I've closed so we can track progress on this ticket.
Hi all,
I know this is a long time coming. We are currently working on the initial solution. I will post updates as we move through the development process.
- Stuart
This is a highly requested feature from our side as well. Websked should respect squad permission settings on website filtering, as well as distributor permission settings.
Sure thing, thanks.
Hi Anais, Thanks for your comment. Actually, I asked that issue to Timothy Keating, the technical delivery manager working for launching Arc to our company. And he suggested I post this issue to idea portal. Could you discuss with him on this issue? Thanks.
contact me any time
Thanks for sharing, Lynda. We have similar issues with our investigative team at WaPo. We're looking into this for the roadmap. Do you mind if I reach out to you to better understand your use cases at a detailed level?
Another example for us at the Boston Globe is that our Spotlight team works on long-term sensitive projects that should not be visible to others in the newsroom. Not having this capability forces them to use other means to develop, write and edit their stories until they are ready to be published and then have to be copy/pasted into Composer and available in websked.
Hi Thomas, I'm going to reach out with some follow up questions. Thanks for submitting your request.