Slack Workspaces
The Slack workspace app connects a Slack team to Bnder so members can receive updates, use Slack commands, and open the same Bnder workspace in the app.
Slack workspaces are different from Discord-backed workspaces. Bnder keeps the Slack installation, Slack membership mapping, and Bnder permissions aligned behind one workspace.
Install or reconnect Slack
A workspace owner should install or reconnect Slack only from trusted Bnder workspace settings or the official Slack install flow.
After installation:
- members can sign in to Bnder with Slack
- Slack workspace membership can provision Bnder workspace access
- workspace notifications can fall back to Slack DMs when browser push is unavailable
- Slack commands can interact with supported Bnder workflows
If Slack messages stop working after token rotation or an app reinstall, reconnect the Slack app from the owner-controlled settings flow.
When does a Slack workspace appear in the app?
A connected Slack workspace appears in Bnder after one of these happens:
- you sign in to Bnder with Slack and the workspace is already linked
- you are added to the linked Bnder workspace through the Slack app flow
- your first valid Slack interaction from the linked Slack workspace provisions your membership
Workspace-specific Bnder permissions still apply after the workspace appears. Slack membership gives you a route into the workspace, but it does not bypass Bnder permissions.
Public ticket reporter sign-in
Public ticket pages always support email-based ticket creation.
Slack-native workspaces can also show Slack sign-in on the public ticket form. This lets an external reporter identify with their Slack workspace identity instead of entering an email address.
Slack reporter sign-in:
- opens a secure API-hosted popup
- works on
bnder.pageand customer-managed custom domains - does not create a full Bnder app account for the reporter
- creates a short-lived reporter session for ticket creation
- stores a Slack reporter identity on the ticket so agents see the Slack reporter name instead of a synthetic fallback email
Discord-backed workspaces can show Discord reporter sign-in instead. Slack-native public ticket pages do not show the Discord option.
Notifications
Bnder can send Slack DMs for workspace notifications when a member belongs to the connected Slack workspace.
Browser push is attempted first when the user enabled it. If browser push is unavailable or no registered browser accepts the notification, Bnder can fall back to Slack DM for Slack workspaces.
Slack DM fallbacks are used for supported task, ticket, calendar, milestone, file, booking, billing, and seat notifications. See Notifications for the full channel order.
Slash command behavior
Slack slash command replies are private by default.
Start the command text with --public when the response should be posted to the channel.
Bnder only continues Slack threads where the Bnder app itself has already replied. Messages from external Slack Connect workspaces do not automatically add those external users to your Bnder workspace.
What happens if I leave the Slack workspace?
If you are removed from the linked Slack workspace, Bnder removes your Slack workspace membership during the scheduled Slack member cleanup.
After that cleanup has run:
- the Slack workspace no longer appears in your Bnder app workspace list
- the related Slack workspace membership is removed from your account data
- app access that depended on that stored Slack workspace membership is revoked
Slack membership changes are not always reflected instantly because the cleanup runs in the background.
Troubleshooting
If a member cannot see the Slack workspace in Bnder:
- confirm the Slack workspace is still connected by an owner
- confirm the member still belongs to the Slack workspace
- ask the member to sign in with Slack again
- check that the member has the needed Bnder permissions
If Slack DMs are not delivered:
- confirm the member can receive messages from the installed Bnder Slack app
- reconnect the Slack app if the workspace recently reinstalled or rotated tokens
- check whether browser push delivered the notification first