---
title: "Project notifications in Microsoft Teams and Slack"
description: "Project notifications in Slack and Microsoft Teams with Planitude: what reaches the channel, noise filters, the Monday summary, Teams Workflows and a Gantt tab."
url: https://planitude.app/blog/teams-slack-project-notifications
language: en
---

# Project notifications in Microsoft Teams and Slack

The updates that matter, in the channel where your team already works: completed tasks, delays on the critical path, deadlines and the Monday summary. How to set them up, including Teams Workflows.

by Planitude Team · Published October 2, 2026

Project notifications have a bad reputation: too many messages, almost all irrelevant, until someone mutes the channel. The result is that the one important piece of news of the week, a delay on a critical task, goes unnoticed.

Planitude notifications for **Slack** and **Microsoft Teams** start from the opposite principle: post little, and only what changes the finish date or someone’s work. This article explains what reaches the channel, how noise is kept down and how to connect both tools, including setting up Teams Workflows after the retirement of Office 365 connectors.

> **Key takeaways**
>
> - The channel receives **completed tasks, date changes on critical tasks and milestones, new assignments, deadlines and overdue tasks**, plus an optional Monday summary.
> - Updates that arrive close together are **grouped** into a single message, in the language and time zone chosen for the channel.
> - On **Slack**, *Add to Slack* is all it takes; on **Teams** you use a Workflow, because Office 365 connectors were switched off in May 2026[^1]. Teams can also show the **Gantt chart in a tab**.

## The plan where your team already works

People working on a project spend their day in a chat tool, not in the scheduling tool. Bringing updates into the channel means the team learns about a delay when it happens, not at the next meeting, and the project manager does not have to type the same message every time the plan changes.

Each Planitude project can post to **one Slack channel** and **one Teams channel**. The settings are inside the project, under the **⋯ › Notifications** menu, and are reserved for the owner and people with the edit role.

## What reaches the channel

You choose which of these events to post:

| Notification | When it arrives |
| --- | --- |
| Task completed | When a task reaches 100% |
| Dates changed | Only for critical tasks and milestones |
| New assignment | When a person is added to a task |
| Deadlines | At 8:00, for tasks due on the next working day |
| Overdue tasks | At 8:00, for tasks past their finish date and not completed |
| Weekly summary | Monday at 9:00 |

Each message includes the task name and key, the dates and a link that opens the task in Planitude. On Slack, messages are built with Block Kit, Slack’s format for structured messages[^5]; on Teams, with an Adaptive Card.

## Less noise: filters and grouping

The most important filter is also the least visible: a date change is posted **only if the task is critical or a milestone**. Moving a task with ten days of float does not change the delivery date and does not interrupt anyone.

The second tool is **grouping**. When the plan is recalculated, many tasks change at once: instead of ten messages, the channel receives one. The window can be set to immediately, 2, 5, 15, 30 or 60 minutes; the default is 5 minutes.

Finally, each channel has its own **language** (Planitude’s 10 languages) and **time zone**, so 8:00 deadlines arrive at 8:00 for the people reading them. You can send a test message or pause notifications at any time.

## The Monday summary

The weekly summary is the most useful notification for coordinators. Every Monday at 9:00 it reports:

- actual **progress** compared with what the plan expected;
- the **delay against the baseline**, if one has been saved;
- the **upcoming milestones**;
- the finish date with an 80% probability (P80) from the **Monte Carlo simulation**, if it is turned on for the project.

In practice it replaces the status message the project manager writes by hand at the start of the week, with figures calculated from the plan.

## Slack: connecting in three steps

Planitude connects to Slack with OAuth, the flow in which an app requests permissions and the person installing it approves them[^4]:

1. in the project, open **⋯ › Notifications › Slack** and click **Add to Slack**;
2. choose the workspace and allow access;
3. choose the **channel**: public channels are available right away; for a private channel, invite the app first with `/invite @Planitude`.

Then select the notifications, grouping, language and time zone, and send a test message. The connected channel also gets the `/planitude status` command, which shows the project status only to the person who typed it; it only sees projects connected to that channel.

## Microsoft Teams: Workflows after the end of Office 365 connectors

For years the easiest way to post to a Teams channel was an Office 365 connector. Microsoft has retired them: the final shutdown took place between 18 and 22 May 2026, and the recommended replacement is Power Automate **Workflows**, starting from the *Post to a channel when a webhook request is received* template[^1].

Setup takes a couple of minutes:

1. in Teams, open the channel, choose **⋯ › Workflows** and look for the webhook alerts template (*Send webhook alerts to a channel*);
2. name the flow, check the team and channel, and save;
3. at the end, Teams shows the **webhook URL**: copy it[^2];
4. in Planitude, open **⋯ › Notifications › Microsoft Teams**, paste the URL, click **Connect** and send a test message.

Planitude only accepts Power Automate Workflow addresses and rejects old connector URLs, explaining what to do instead. One note: messages sent through Workflows appear under the Workflows bot identity, because the name and icon cannot be customized[^1]. That is a Microsoft limitation, not a limitation of the integration.

## The Teams tab with the Gantt chart

Besides notifications, Teams lets you add a **tab** to a channel: a web page embedded in the client and configurable for each team[^3]. The Planitude tab shows the project’s Gantt chart in read-only mode, with zoom and task details, and a button to open it in Planitude.

Adding it requires the Planitude app for Teams, which the tenant administrator can upload to the organization’s app catalog. Each channel member signs in with their own Planitude account and sees the project only if they have access to it; the tab shows no costs, notes or people.

## Security and privacy

- The Slack token and the Teams Workflow URL are **encrypted**, and the URL is only shown abbreviated on the page.
- Requests coming from Slack are verified with the app’s signature.
- Planitude **does not read** channel messages: it only posts project updates.
- When you disconnect, the credentials are deleted immediately; messages already posted stay in the channel.

For the other connections available, from Jira to AI assistants, see the [guide to integrations](https://planitude.app/blog/planitude-integrations-guide) and the [Integrations](https://planitude.app/integrations) page.

**Try Planitude with your own plan** [Create a free account](https://planitude.app/signup)

## Frequently asked questions

### Do notifications reach people who do not use Planitude?

Yes. Every member of the channel can read the messages; opening the task from the link requires an account with access to the project.

### Can I connect several channels to the same project?

Each project can post to one Slack channel and one Teams channel. Several projects, on the other hand, can post to the same channel.

### Does my old Teams connector still work?

No. Microsoft completed the shutdown of Office 365 connectors on 22 May 2026[^1]. Create a Workflow in the channel and paste the new URL into Planitude.

### Who receives deadlines by email?

Email reminders are separate from channels: each morning they go only to people with tasks due or overdue, and everyone can turn them off from their profile.

## Sources

Every fact about the products mentioned comes from these official pages, checked in September 2026. Prices are list prices, in the currency and billing period shown by the vendor, and may change.

[^1]: [Microsoft 365 Developer Blog: retirement of Office 365 connectors in Teams](https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/)
[^2]: [Microsoft Support: send messages in Teams using incoming webhooks](https://support.microsoft.com/en-us/teams/apps-service/create-incoming-webhooks-with-workflows-for-microsoft-teams)
[^3]: [Microsoft Learn: tabs in Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/platform/tabs/what-are-tabs)
[^4]: [Slack Developer Docs: installing with OAuth](https://docs.slack.dev/authentication/installing-with-oauth)
[^5]: [Slack Developer Docs: Block Kit](https://docs.slack.dev/block-kit/)

## Try Planitude with your own plan

Create a free account, import your .mpp file or start from a template: within minutes you will see the Gantt chart with dependencies, calendars and the critical path.

[Create a free account](https://planitude.app/signup)