r/Slack

Our company has been using Slack for years and at this point people treat it like a dumping ground for everything. I've randomly come across passwords, customer info, IDs, and even payment details sitting in old channels.

The bigger concern is something eventually getting leaked. I'm trying to figure out how other security teams are handling sensitive data in Slack before it actually gets exposed.

Are you using any tools to detect this stuff as it's shared and take action on it? Historical visibility would be useful too since I'm sure there's plenty sitting in old channels that we haven't found yet.

If you developed a Slack app, you know that you need to have it installed on at least 5 active workspaces to be able to submit it to the marketplace.

So it's a chicken/egg problem - how do I get installs if it's not on the marketplace?!

Let's help each other - I will install your Slack app on my workspace, and hope you will install mine also.

Leave a comment with your Slack app and I will install it on my active workspace.
Mine is AutoThreads.

Hi everyone,

I am setting up a new project and wanted to know what's the best or the trending PM tool to setup alongside slack since I am coming from using Jira in the past just wanted to what's out there. Appreciate if you all can give some insights. Thanks

I keep running into this with sensitive projects. You start with five people who all need to be there. Then someone adds an assistant. Someone else adds a contractor. A week later there are 15 people in the chat and nobody seems sure who invited half of them.

The weird part is that every addition makes sense in the moment. Nobody thinks they are opening up the group too much. It just happens one person at a time until the “small trusted circle” is not that small anymore.

Has anyone found a good way to prevent this without causing some sort of argument?

I'm researching how teams actually solve the "whose turn is it?" problem in Slack and I'd love real-world answers before I build anything.

What I keep seeing at companies I've worked with:

- A pinned spreadsheet that's outdated within three weeks

- A /remind that happily pings people who are on vacation

- Workflow Builder attempts that die because it has no "next person in the list" step and no memory of who was last

- One person (usually the same one) manually tagging whoever is next

If your team runs any recurring duty through Slack — support triage, code review assignment, meeting facilitation, on-call handoff:

1. What do you use today (app, spreadsheet, homegrown bot, nothing)?

2. What breaks most often — vacations, fairness, timezones, people forgetting?

3. Did you try one of the existing rotation apps and drop it? Why?

Not selling anything in this post — genuinely trying to understand if this is a real pain or just my bubble. I'll share a summary of the answers in the comments if there's interest.

Having notification issues - is this a common problem?

Can't seem to make them work.

Thanks

In my last startup Slack was awesome until we reached around 100 people then it became a mess. Any interesting replacements? Just curious to try stuff out. Seems unreasonable this field is not being disrupted.

I saw Buzz come out by Jack Dorsey but honestly the UI is much worst then Slack. Also saw Glue but honestly seemed like a total Slack rip off…

Would love to hear suggestions thanks 🙏🏼

Hello,

In my organization, we are using both Slack and Teams.

I would like to have one channel in Slack that is synced into Teams, where messages created in Slack will be created in Teams, and vice versa.

I tried SlackBridge, since this is a free app, but without success: It was installed succesfully into Slack and Teams as well, however, messages in one app is not transfered into the 2nd app.

Alternatively, I tried to sync using Workato, however, I didn't find a Microsoft Teams connector as a trigger (but only Workbot for Microsoft Teams).

What's the difference between Microsoft Teams connector and Workbot for Microsoft Teams connector?

Is there any recommended free app?

My manager has workspace admin for slack and tracks location using the IP address in access logs. I find this a little intrusive. Is there a way to mask the ip address in slack?

Hi All,

I manage a professionals community on Slack and we're attempting to track churn and disengagement. I've used the Slack analytics feature and it's ok. However, I've built an integration to pull Slack engagement metrics on members (ie: last message they sent, my last reaction with this member) with Luma to get a better idea on how members are disengaging.

It got me thinking, what Slack metrics do you keep track of for your community? Moreover, are there any metrics that you wished you have but are hard to visualize or Slack doesn't provide?

Hi Hi - I’m an incoming grad student and I thought making a slack for my cohort would be a good way for us to communicate. there are only 16? students and we share all classes.

i’m wondering if anyone has some tips on how to best set up the workspace? i’ve used slack before but ive never set one up.

should each class have a channel? or just homework help or something?

any tips would be greatly appreciated!!

🫶

I’ve been building a Slack app and I’m at the point where I need a few teams willing to actually test it.
I don’t want this to come across as advertising, so I’m not dropping any links here.

The problem I’m working on is pretty simple: important decisions happen in Slack, but a few weeks or months later it can be surprisingly hard to figure out what was decided, why the team made that decision, and what context led to it.

The app lets a team capture a decision from Slack, preserve the context around it, and create a structured decision record that can be referenced later.

The goal isn’t to replace Slack or change how a team communicates. I’m trying to see whether capturing decisions this way is actually useful when it’s part of a team’s normal workflow.

I’m looking for a handful of Slack teams willing to install it, try it with real decisions, and tell me what works, what’s annoying, and what you’d change.

If you’re interested, message me and I’ll send you the details. I’d also be curious to hear from anyone who’s dealt with the problem of losing the reasoning behind old Slack decisions.

Thanks!

I've been building a few Slack apps and need some testers.

I don't want to advertise, so I won't drop any links, but Slack requires 5+ workspaces to install and try an app before you can submit it for review, and this if for each app. I've got three apps which:

- DMs your team a few questions on a schedule, collects the answers, and posts a clean digest to your channel instead of everyone hopping on a call

- randomly (but fairly) assigns a code reviewer from your team so you're not always pinging a channel or leaning on the same two people

- react to any message with an emoji and it translates it right there in the thread

We actually do all three of these manually at my current company, as someone chases standup updates, eyeballs who's free to review, or copy-pastes translations, so I started automating them one by one and figured other teams probably deal with the same stuff. Who knows, might keep improving on these as I go.

If any of them are useful to you and you're up for testing, message me and I'll send the link. If testing's not your thing, I'd still be curious whether any of these would actually help your team, or if you've already got this stuff handled.

Thanks!

Hey, anyone one of you really tried to save your time for daily tasks by just trying to make a bot. It costs minimal and is so time saving.
Just a week ago I created a slack bot for a Michigan Based company and it saves them alot of time with reporting and working.

Hey everyone,

I wanted to share a workflow adjustment we made recently that saved our team from constant context switching and notification overload.

A few months ago, we realized that our Slack channels were becoming a black hole for basic questions. Team members would ping us for standard procedures, playbooks, or client details. While it’s great to be helpful, it meant constant interruptions and an incredible amount of "noise" throughout the day.

Instead of letting Slack dictate our day, we decided to make Notion our official company OS. We brought all our playbooks, data, and context into one single place.

We set a simple rule for the team: Before asking a question in Slack, ask Notion AI first.

Because everything is indexed in one place, the AI can scan our playbooks, past decisions, and documents to give an accurate answer.

Only if the team member cannot get the answer from Notion AI do they ping us on Slack.

The Results

Reduced noise by 80%: The constant stream of repetitive questions has vanished.

Fewer interruptions: We've reclaimed our focus and can spend more time working on the business instead of managing chats.

Faster onboarding: The team learns faster because they get immediate, context-aware answers.

The magic is that everything the team needs from client guidelines to marketing playbooks is in one place, making our AI system highly reliable.

If you are struggling with Slack overload, I highly recommend building a unified knowledge base and letting your team query the AI before escalating.

I want to be completely honest with you: this isn't a "set it and forget it" system. In the beginning, we noticed that a few questions didn't get answers because the AI lacked the context.

Every time that happens, we treat it as a quick fix: we just update the existing documentation or add a new page if the topic wasn't covered. It takes a little maintenance, but it has been absolutely worth it to cool down Slack and keep the team fully aligned.

If anyone is interested in how we set this up alongside Slack, including our internal Slack communication framework, just let me know in the comments! I didn't want to make this post too long, but I'd be happy to do a deeper dive on that in my next post.

P.S. If you're the founder still in the middle of every decision, still the person the whole company waits on, still telling yourself you'll fix the structure "once things calm down."

I write about building the operational backbone that lets a founder actually step back every Thursday. Was a COO for 20+ years, so this is genuinely my bread and butter. Free to join here