51–54 of 54 posts
Yet another 'digital container' of disparate information to house your data and make it difficult for someone find it across an organisation. As someone who was working in a scale up I found that we had information spread across coda, wiki, markdown, tickets, collaborative whiteboards (Miro), git issues, google docs, coda, (insert random lastest cool SaaS that someone stumbled across one night and used the company ca…
Great, now we can post a Slack link to a Confluence page that links back to a Slack Canvas that links to a Google Doc that links to a Slack thread that says to look in Jira for that outdated video on Sharepoint.
Earlier quoted context omitted.
Long ago Mozilla started making all such decisions on mailing lists, because the meetings at water coolers never get documented, and because you can't meet a colleague who lives 10,000 miles away over a water cooler (or at least not very often).
Interestingly enough, fully-remote companies have an advantage here - such "water-cooler" discussions and decisions still happen, but more commonly over Slack and email than in person (and even in-person discussions can be recorded, although few people think of that in advance).
Earlier quoted context omitted.
Bear in mind that at this time, and for many years, data retention policies simply do not apply to uploaded files in a given channel (IIRC it does apply to global retention, but I'm not totally sure of the current behavior). There's a sensitive channel with a short retention period in a Slack for a company I do some consulting for and every few months I remind the admins that images/PDFs/etc that are uploaded to the…
It sounds like there’s no file retention policy specified for that Slack workspace. It’s possible to set a policy specifically for files. https://slack.com/help/articles/203457187-Customize-message-...