How Teams channels work inside projects

Once Teams is connected (see "Microsoft 365: SharePoint, Teams, and Calendar" for that setup), each project can mirror its conversation into a real Teams channel. This article is about how that mapping behaves day to day, what posts automatically, whether replies come back, and how attribution works for partners.

A project manager or admin opens the project and maps it from the Teams channel panel. Current lists the Teams you've joined and their channels, pick a team, then a channel, and save. This uses your own Microsoft connection, so if you haven't connected yet, the panel points you to Settings first.

1. 1
   Open the project

   The Teams channel panel appears on the project detail page for anyone who can manage projects.
2. 2
   Click Map to Teams

   Current calls Microsoft to list the Teams and channels your account belongs to.
3. 3
   Pick a team, then a channel

   The channel list depends on which team you selected.
4. 4
   Save the mapping

   New comments on this project now mirror to that channel. You can change the channel or unmap it later from the same panel.

Where channels are created automatically, the New project dialog asks Who should hear about it? It starts with you and the company's account managers, and you can add or remove people. Once Current has created the channel, it posts one welcome there (for example "@Ana Ruiz @Ben Cole: the Northside Dental Server Refresh project has been created." with an Open in Current link) that @mentions each person you picked. Someone Current can't find in Microsoft 365 is named in plain text instead of tagged. The welcome is posted once: if Teams doesn't confirm it, Current doesn't send it a second time.

On the project page, the Access & Teams section links straight to the channel with Open channel in Teams and says who the welcome tagged.

Two kinds of messages reach a mapped channel. Comments you or your team write on the project post there, attributed with your name. Separately, project alerts (a task getting assigned, a task becoming unblocked, a health score dropping, and similar events) can also post to the channel if you've turned Teams on in your notification preferences.

In Current, the project's conversation reads from oldest at the top to newest at the bottom, with the comment box underneath; a long conversation scrolls inside its box and opens on the newest message. Alerts Current posts to the channel are not brought back as comments. One that already came back shows as a short Alert line rather than a message from whoever posted it, and the AI assessment in the project's Health card never reads an alert as someone's words.

A comment alerts everyone it @mentions, and the task's assignee even when nobody is mentioned. The bell in Current always gets the alert. On top of that, each person is reached in exactly one of three ways, tried in this order:

1. 1
   Tagged in the project's Teams channel

   When the project is mapped to a channel and the person is a member of that channel, the channel post tags them. The post names the author once, keeps the comment as written with each @name turned into a real Teams tag, and ends with the task number and name and an Open in Current link.
2. 2
   A Teams chat from you

   When the person isn't in the channel, or the project has no channel, Current sends them a one-to-one Teams chat from your own Microsoft account: who mentioned them, on which task, the comment, and the same Open in Current link. This needs you to have connected Microsoft 365 in Settings, and a chat is never sent from anyone else's account.
3. 3
   An email

   When neither of those can reach them, the alert goes by email, with one line saying why (for example, that they aren't in the project's Teams channel). Their own email preferences for mentions and comments still apply.

• A person reached in Teams doesn't also get the email.
• If Teams hasn't confirmed an alert, it goes by email instead, so nobody is missed: within about ten minutes on weekdays; comments posted over the weekend are emailed on Monday.
• You're never alerted about your own comment. Mention yourself and the thread says so.
• Mentions of your partners in the portal work as before and aren't part of this.

Your team sees a short line under each comment saying who it reached and how. Partners in the portal never see it. Right after you post it reads "Reaching" followed by the names, and it updates on its own for about five minutes while Teams answers.

The reasons in brackets: not in the channel; channel members couldn't be checked; no Teams account found; Teams account couldn't be checked; the Teams chat didn't go through; Teams chat isn't allowed for the sender; the sender hasn't connected Microsoft 365; the Teams post didn't go through; Teams didn't answer in time. "In-app only" carries one of two reasons: the person turned email alerts off for mentions and comments (email alerts off), or their email address is blocked after messages to it bounced (email address is blocked). A person whose account is turned off isn't alerted at all, and the line leaves them out.

Reaching people in Teams uses two Microsoft permissions on top of the ones Current already asks for. A Microsoft 365 global admin approves them once for the organization: a Tenant Admin presses Manage on the Microsoft 365 card at the top of Settings › Integrations and chooses Re-approve under Platform, signed in at Microsoft as a global admin. Nobody reconnects: each person's Microsoft connection picks up the new permissions on its next refresh.

A comment with no mentions alerts the task's assignee. On a task synced with your PSA, the assignee follows the task's primary resource: when the PSA moves the task to someone else, the next sync moves it in Current too, the new person gets the usual "Assigned to you" alert, and comments alert them from then on. If someone reassigns the task in Current, that choice is kept until the primary resource changes in the PSA again.

Teams isn't a one-way broadcast. Current periodically checks each mapped channel for new messages and replies, and anything your team writes there (including replies buried in a thread) lands back in the project's comment history in Current. The first time a channel is mapped, Current only starts watching from that point forward, so you won't get flooded with the channel's older history.

Partners (external clients using the read-only portal) don't have a Microsoft connection of their own, so their co-managed comments can't post to Teams directly. When a partner adds a comment that's visible to your team, Current posts it to the mapped channel under a connected staff member's identity, with the message clearly labeled with the partner's name followed by "(partner)" so your team always knows the comment came from the client, not from a teammate.

Any mapped project can turn on a morning standup post. A short automatic summary posted to the channel on weekday mornings (8:30am ET) listing what was finished yesterday, what's due today, and what's overdue, along with the project's health indicator. It's off by default and is a per-project switch, right next to the channel mapping. There's no workspace-wide standup setting.

If Current can't list your Teams and channels automatically, the panel switches to manual entry: two plain text fields for Team ID and Channel ID. In Teams, open the channel, use "Get link to channel," and paste the IDs from that link.

• An empty or failing picker is almost always a missing Channel.ReadBasic.All permission on the Microsoft 365 app registration, see "Microsoft 365: SharePoint, Teams, and Calendar" for the full permission list.
• Reconnecting your Microsoft account in Settings can also resolve a stale or expired connection.
• The manual Team ID / Channel ID fields work regardless of that permission, so mapping never has to be blocked entirely.