Slack already supports screen sharing in calls, but now it's adding a dose of interactivity to the mix. Rolling out to Slack's desktop apps today, interactive screen sharing will allow other people on a call to collaborate on whatever is being shared to make their own edits or highlight areas of interest.
The feature is essentially geared toward breaking down the barrier created by distance, enabling people to work on a project as if they were in the same room. While sharing a screen in a call, you can now hit the "share control of your screen" button to let others participate. Each member of the call will get their own cursor "along with the ability to type, edit, scroll, and click through the contents of the shared screen," Slack says. When you're not sharing control, members of the call can highlight areas of interest by temporarily drawing on the screen.
Slack says it has already seen companies take advantage of interactive screen sharing for things from IT troubleshooting and programming to collaborating on fielding customer tickets. We're sure to see more uses crop up as the feature rolls out to everyone.
According to Slack, interactive screen sharing is available to paid plan users on the latest versions of its Windows desktop and Mac apps.
Dan Thorp-Lancaster is the Editor in Chief for Windows Central. He began working with Windows Central as a news writer in 2014 and is obsessed with tech of all sorts. You can follow Dan on Twitter @DthorpL and Instagram @heyitsdtl. Got a hot tip? Send it to email@example.com.
Slack is really good I see a lot of companies using the "free" version. I like it better than teams currently only issue if corporations going towards the 365 method.
I prefer teams, because of integration with company account, sharepoint, planner, tfs, also because is included in office 365 ... what exactly don't you like in teams?
Get the best of Windows Central in in your inbox, every day!
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.