Note both slack accounts have to be on the paid plan. This isn't mentioned anywhere but makes it much less useful than they are presenting it to be.
Third paragraph:
> It’s officially out of beta today and available for all paid plans.
Slack Shared Channels
61–70 of 72 posts
Re: Slack Shared Channels
#62> Using a shared channel, when the junior auditors start, they see a full history of prior work.
Well a full history of prior chat and giphy memes. Meanwhile I'll be reviewing past Jira sprints.
Re: Slack Shared Channels
#63This feature is close to useless for me since the admin of the slack account has to “connect” the two teams/domains/whatever - how does that enable free and ad-hoc collaboration in a medium-to-large organisation??? I’m used to tools like Dropbox, email, Asana, G-suite where you can mostly just collaborate with whomever you want around the world. I think slack is missing a huge opportunity by keeping it so locked down…
Keeping it locked down is how they keep enterprise security teams happy, and selling to enterprises is how they make a lot of money.
..and that's how rogue use of other tools start and how "shadow IT" became a thing :-) .. these super locked down systems become "security theatre" and create a false sense of amazing data governance and buttoned up security.
Re: Slack Shared Channels
#64WHERE IS THE DARK MODE SLACK ????!
Re: Slack Shared Channels
#65The issue with the channels are the same than communicating over slack: You customers are feeling like they can ask any question and get an answer in 1 minute, and if you dont answer them straight away then they are unhappy. Definitively not something I recommend
Don’t blame the tool for mismanaged expectations.
but the medium is the message
Re: Slack Shared Channels
#66The issue with the channels are the same than communicating over slack: You customers are feeling like they can ask any question and get an answer in 1 minute, and if you dont answer them straight away then they are unhappy. Definitively not something I recommend
I don't think I've experienced either side of this. I've never seen people who otherwise have reasonable expectations of response time go crazy because of Slack. And I have never, ever seen someone with unreasonable expectations of response time behave well just because it's e-mail. Especially since e-mail has been put onto smartphones, I don't really see a whole lot of difference in how people behave based on the si…
the UI s definitely differentiate. Typing indicators, compact display, persistent reply prompt ... these things prime the users over how to use the box.
Re: Slack Shared Channels
#67WHERE IS THE DARK MODE SLACK ????!
Re: Slack Shared Channels
#68Earlier quoted context omitted.
Is this intended for support? We use single channel guests at the moment to collaborate on projects with external companies without any issue. This seems to be geared towards that.
I imagine it's intended for any use case in which you want to communicate with people outside your company via slack, but don't want to invite them into your org. I was responding to these comments: >You customers are feeling like they can ask any question and get an answer in 1 minute, and if you dont answer them straight away then they are unhappy. Definitively not something I recommend >Don’t blame the tool for mi…
So am I, "Don’t blame the tool for mismanaged expectations.". This is correct IMHO. Inviting customers in that expect support is setting their expectation that they'll get support in real time. I could think of potentially two of our customers that pay enough for us to consider this. The tool just needs to be used the correct way.