Connect your DevStride organization to Slack and members receive direct mentions and the item activity they choose as personal messages from the DevStride app in Slack. There are no channel posts and no slash commands: an administrator connects the workspace once, and each person switches on what they want in their own notification settings.
app.devstride.com for production notifications. A connection made in a development environment does not connect production.team:read), member profiles and email addresses (users:read, users:read.email) so it can match members to Slack accounts, basic public-channel information (channels:read), and permission to send messages as the app (chat:write).On a new connection, DevStride also attempts to send the connecting user a Slack message saying “Slack integration with workspace name was successful!” The matching-email prerequisite applies to this confirmation too. Use the connected workspace name in DevStride and a fresh notification test to verify the full setup.
You do not create a Slack app, configure a webhook, or paste an API token. Always start from DevStride so the workspace is linked to the right organization.
Each recipient completes these steps in DevStride:
The direct-mention checkbox and the Slack activity grid are separate controls. Review both, including any existing selections. Email, Microsoft Teams, and DevStride Notification Center preferences are configured separately.
If the checkbox is disabled with Slack Integration Required, or the Slack activity tab is absent, the selected DevStride organization has no loaded Slack connection. Ask an administrator to connect it, then reload Notification Settings.
Open the connected Slack workspace and look for the DevStride app conversation. You can find the app through Slack's search or Apps area. Notifications arrive as personal app messages; there is no channel picker in this setup flow.
The workspace connection authorizes delivery for matching recipients. Each recipient still needs to enable their DevStride preferences, but there is no separate personal installation step like the Microsoft Teams setup.
If a message is present in the app conversation but no desktop or phone alert appears, check Slack's own notification settings, paused notifications, and device notification permissions. Those controls are separate from DevStride delivery.
Setup is complete when the recipient receives the message and can open the linked item. The installation confirmation sent to the connecting user does not verify another recipient's preferences or email match.
To test conditional notifications, have another member make a change covered by the recipient's Slack activity/role selections. Create a fresh event after changing preferences or repairing the connection.
| What you see | What to check |
|---|---|
| Slack settings are unavailable in DevStride | Confirm the selected organization and ask an administrator to verify your Manage Integrations permission. |
| Connect Slack Workspace does not open Slack | Check the browser's blocked pop-ups, then retry from the Slack integration page. |
| Slack asks for approval or blocks installation | Contact your Workspace Owner or app manager. After approval, complete the connection from DevStride. |
| The authorization link expired, or connection was interrupted | Start again with Connect Slack Workspace instead of reusing an old authorization tab. |
| New installation fails while sending the confirmation message | Check that the connecting person's DevStride email exists as an active Slack account in the chosen workspace. If it matches, contact DevStride support with the error and approximate time. |
| The wrong workspace appears | Have an administrator remove that connection and connect the intended workspace. Removal interrupts Slack delivery through that connection. |
| Slack Integration Required or no Slack activity tab | Connect Slack for the selected organization, then reload Notification Settings. |
| Connected, but one person receives nothing | Compare that person's Slack and verified DevStride emails, confirm active memberships and item access, and check both direct-mention and conditional preferences. Test with a new event from another member. |
| Everyone stops receiving messages after the Slack app is removed or its authorization is revoked | Ask the administrator to reconnect from DevStride. If necessary, remove the stale connection first, then authorize again and run a fresh test. |
| Messages appear in Slack without a banner or sound | Check Slack's notification preferences, paused notifications, and device permissions. |
| A development or sandbox test is silent | Ask DevStride support to confirm Slack delivery is enabled for that environment. |
When contacting support, include the DevStride organization and environment, Slack workspace name, affected recipient email, test item number, approximate time and time zone, and any error shown. Do not send passwords or app tokens.
For the organization: open Configure Settings → Integrations → Slack, select Remove, and confirm Remove Connection. This disconnects Slack delivery through that connection. It does not change users' Email, Teams, or Notification Center preferences. To remove the app from Slack itself as well, have your Slack administrator manage its installation there.
For yourself: turn off Slack under Notify Me of Direct Mentions Via and clear the selected rules on the Slack conditional-notification tab. You do not need to disconnect the organization's workspace to opt out.
list_slack_installations and delete_slack_installation read and remove the same connectionMicrosoft Teams
Get DevStride notifications as personal Microsoft Teams messages: an administrator connects your Microsoft 365 organization and makes the app available, then each person adds the app, chooses what to receive and sends themselves a test.
Connected Apps
See which apps you have authorized through OAuth to act on your DevStride account — AI clients such as Claude or Cursor — and revoke any you no longer use.