---
title: "Slack Integration for Project Management | Orangescrum"
description: "Bring Orangescrum into Slack. Send project activity to the right channel, run slash commands, and create or update a task from a message without leaving."
canonical: https://www.orangescrum.com/integrations/slack
---

# Slack Integration for Project Management | Orangescrum

> For the complete documentation index, see [llms.txt](https://www.orangescrum.com/llms.txt).

[Home](/) / [Integrations](/integrations) / Slack

Slack

# Slack Integration for _Project Updates and Actions_

Put project activity in the channel your team already has open, and let people act on it there. Slash commands, interactive messages, and one channel per project.

Available inCloud[Self-Hosted](/self-hosted "Self-Hosted - included")Open Source

[Explore Self-Hosted →](/self-hosted)[Book a Demo](https://calendly.com/orangescrum)

Available in the Self-Hosted edition - runs on your own servers

This capability is available in the **Self-Hosted (on-premise)** edition. It is not part of the Cloud edition today.

## What does the Slack integration do?

The Slack integration connects Orangescrum projects to Slack channels. You install the Orangescrum app into your workspace, map each project to the channel that owns it, and task activity is posted there as formatted messages. From that message people can act, using either a slash command or the buttons on the message itself, so a small update does not require opening another tool. Each Slack account is linked to an Orangescrum user, so any change made from Slack is attributed to the right person.

The problem

## Why project updates _go unread_

The team lives in Slack

People have Slack open all day and open the project tool when somebody chases them.

✓ Activity arrives in the channel they are already in.

Acting on an update means switching tools

A one word answer costs a context switch, so it gets postponed and then forgotten.

✓ Slash commands and message buttons handle it in place.

One firehose channel gets muted

Every project posting to the same channel means nobody reads any of it.

✓ Map each project to its own channel and choose what gets posted.

What you get

## Orangescrum, _inside Slack_

Notifications, commands, and actions, with each Slack user tied to their Orangescrum account.

-   ### Task activity in the channel
    
    Task events are posted to the Slack channel mapped to that project, so the people who care see them without going looking.
    
-   ### Properly formatted messages
    
    Updates are built as Slack Block Kit messages rather than plain text, so they are readable and carry the actions with them.
    
-   ### Slash commands
    
    Run Orangescrum commands from the Slack message box, without opening the app.
    
-   ### Act from the message
    
    Buttons and dialogs on the message let someone create or update a task straight from the conversation.
    
-   ### Channel mapping
    
    Each project points at its own channel, so a team only sees the work that belongs to it.
    
-   ### Slack user to Orangescrum user
    
    Accounts are linked, so an action taken in Slack is recorded against the right person in Orangescrum.
    
-   ### Signed requests
    
    Every request from Slack is verified against your signing secret before it is accepted.
    
-   ### Event log
    
    Deliveries and actions are recorded, so when somebody says the message never arrived there is an answer.
    

How it works

## How to _set it up_

1

Install the app

Create the Orangescrum Slack app from the supplied manifest and install it into your workspace over OAuth.

2

Link accounts

Each person links their Slack account to their Orangescrum user once, so their actions are attributed correctly.

3

Map projects to channels

Decide which project posts into which channel, and which events are worth posting.

4

Work from the conversation

Your team uses slash commands and message buttons, and Orangescrum stays up to date.

Who it's for

## Good for teams that _live in Slack_

Product and engineering

Teams that coordinate in channels and want delivery updates in the same place.

[Learn more →](/solutions/it-project-management-software)

Agencies and services

Client work run in channels, with task updates next to the conversation about them.

[Learn more →](/solutions/marketing)

Operations and support

Teams that need to see and act on incoming work quickly.

[Learn more →](/solutions/business-operations)

Availability

## Which edition includes _what_

Orangescrum runs as managed cloud, self-hosted on your own servers, or as the open-source Community Edition. Here is exactly what each one includes.

The Slack integration is part of the Self-Hosted edition.

| Capability | CloudManaged SaaS | Self-HostedOn-premise / private cloud | Open SourceCommunity Edition |

| Task activity posted to Slack channels | ✗ | ✓ | ✗ |
| Block Kit formatted messages | ✗ | ✓ | ✗ |
| Slash commands | ✗ | ✓ | ✗ |
| Create and update tasks from a Slack message | ✗ | ✓ | ✗ |
| Project to channel mapping | ✗ | ✓ | ✗ |
| Slack account linked to an Orangescrum user | ✗ | ✓ | ✗ |
| Signed request verification | ✗ | ✓ | ✗ |
| Email notifications | ✓ | ✓ | ✓ |

Frequently asked questions

## Slack integration _FAQ_

### Does Orangescrum integrate with Slack?

Yes, in the Self-Hosted edition. You install the Orangescrum app into your Slack workspace, map projects to channels, and task activity is posted there. People can then act on it with slash commands or with the buttons on the message.

### Which edition includes the Slack integration?

The Self-Hosted edition. It is not part of the Cloud edition today, and it is not in the free Community Edition. If Slack matters to you and you are on Cloud, that is worth raising before you commit.

### Can I create a task from Slack?

Yes. Interactive messages and slash commands both lead to creating or updating a task, and because your Slack account is linked to your Orangescrum user, the change is recorded against you rather than against a generic bot.

### Can I control what gets posted?

Yes. You choose which events are posted and which channel each project posts to, so a channel stays useful instead of turning into a feed nobody reads.

### Does every project have to use the same channel?

No. Channel mapping is per project, which is the point. Teams that map everything to one channel usually end up muting it.

### Is it secure?

Requests from Slack are verified against your signing secret before they are processed, and the connection is installed through Slack OAuth. Because this is the self-hosted edition, the Orangescrum side of that traffic terminates on your own infrastructure.

### Does this work with Microsoft Teams too?

Teams is a separate integration with its own notifications, cards, tabs, and bot, also in the Self-Hosted edition. You can run both if different parts of the organisation use different tools.

### Will people see work they should not?

A channel only receives activity from the projects mapped to it, so the boundary is the mapping you configure. It is worth checking that mapping against your project permissions when you set it up.

## Bring your projects into Slack

The Slack integration is included in the Orangescrum Self-Hosted edition, running entirely on your own infrastructure.

[Explore Self-Hosted →](/self-hosted)[Book a Demo](https://calendly.com/orangescrum)

## Related capabilities

[All integrationsSee everything Orangescrum connects to](/integrations)[Microsoft Teams integrationThe same idea, in Teams](/integrations/microsoft-teams)[MentionsPulling the right person into the work](/mention)[Self-Hosted editionRun Orangescrum on your own servers](/self-hosted)