Two ways the bot gets into Slack
- Install the SourceMedium app in your workspace. See Setup for the install URL and permissions.
- Share SourceMedium into a Slack Connect channel. The channel can work without every company installing the app.
@SourceMedium. In a 1:1 DM, type normally.
How store scope is chosen
Once a thread is locked to a store, start a new thread to switch. Results in a shared channel are visible to everyone in that channel.
The selector can preselect your last-used store or the workspace default. Confirm with Use this store before analysis runs.
Messages you may see
I can’t answer in this shared channel yet because one workspace isn’t connected to SourceMedium. Ask an admin to connect that workspace, or use a channel where every company is already connected. I can’t find a data scope that works for everyone here. The people in this conversation do not share a store. Move to an approved shared channel, or ask an admin to update access. I can’t answer in this conversation; some people need the SourceMedium app installed. Each person in a DM or group DM needs the app installed in their own Slack workspace. Use an approved shared channel until then. This thread is scoped to a different organization. Your Slack account cannot use this thread’s tenant. Start a new thread. In a channel, that new thread is still visible to the other participants. Access denied: your Slack account is not approved. Your email is not on this organization’s allowlist. Ask your SourceMedium team to add the domain or the exact email. SourceMedium access for this workspace is currently paused. Billing or lifecycle has paused the workspace. Only SourceMedium can restore it.Related
Multiple stores
How store confirmation works in DMs and channels.
Setup
Install URL, permissions, and who can use the bot.

