> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getthread.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Inbox Channels Deprecation: What's Changing and When

> Channels in Inbox retire on February 28, 2026. Learn who is affected, why Channels are being replaced with Views, and how existing Flows remain unchanged.

## Channels Deprecation in Inbox

**Channels will be retired on February 28, 2026.**

This article explains what Channels are, who this change applies to, and what it means for your Inbox setup.

### Why am I seeing this message?

You’re seeing this notice because your workspace was set up **before Views were introduced**, and still uses **Channels** in Inbox.

Partners who onboarded to Thread after the launch of **Views** no longer see Channels in their workspace and are **not affected** by this change.

### What are Channels?

Channels were the **original way to organize work in Inbox**.

They appear in the left navigation and act as containers for tickets and messages. Channels are powered by **Flows**, which determine which threads appear in each Channel based on filters like board, source, status, or priority.

### What’s changing?

Channels are being **fully retired** on **February 28, 2026**.

This is a planned transition away from the legacy Channels model toward a simpler, more flexible system built around **Views**.

There’s no immediate impact to your workflow today.

### What’s not changing?

**Flows are not impacted**

Your existing Flows will continue to:

* Route tickets and notes
* Apply filters and automation logic
* Send updates to Teams or Slack
* Run exactly as they do today

No Flows need to be recreated or updated as part of this change.

### What are Views?

**Views** are the current and recommended way to organize work in Inbox.

Views let you:

* Create filtered perspectives on threads (e.g. Triage, In Progress, Escalations)
* Save and reuse those filters
* Organize work without relying on Channels
* Get deeper visibility through Views & Insights
* See updates in real-time

Partners who onboarded more recently use Views by default instead of Channels.

Learn more:

* [Setting up Inbox Views](/inbox/views-and-insights)
* [Views & Insights overview](/inbox/views-and-insights)

### What do I need to do right now?

Nothing.

This notice is shared early so you have time to understand what’s changing. Your existing setup will continue to work as-is, and we’ll provide clear guidance as we inch closer to retire Channels.

### How we’ll support you

Between now and February 28, 2026, we’ll:

* Share reminders and updates in-product
* Provide guidance on organizing work with Views
* Ensure Flows continue running reliably
* Make the transition as smooth and predictable as possible

## FAQ

<AccordionGroup>
  <Accordion title="Does this affect everyone?">
    No. This only applies to partners who still have **Channels** in their workspace. Newer partners using **Views** are not affected.
  </Accordion>

  <Accordion title="Will my Flows stop working?">
    No. Flows will continue to run as they do today except without being tied to a Channel.
  </Accordion>

  <Accordion title="Do I need to recreate my workflows?">
    No. There’s nothing you need to change right now.
  </Accordion>

  <Accordion title="Will I lose tickets or messages?">
    No. This change does not remove or delete any data.
  </Accordion>

  <Accordion title="Can I still use Channels today?">
    Yes. Channels will continue to work until they’re officially retired, though we recommend using Views and Teams to set up your workspace.
  </Accordion>
</AccordionGroup>


## Related topics

- [Flows: Automate Thread Routing and Actions in Inbox](/inbox/flows.md)
- [Adding and Removing Contacts in Inbox (HaloPSA)](/inbox/adding-removing-contacts-in-halo-psa.md)
- [Views and Insights in Thread Inbox](/inbox/views-and-insights.md)