# Can I license Slack Connect messages to AI?

> Searching whether you can sell Slack Connect messages to AI? Licensing them is murky. An export carries partner messages, and Slack's text is silent on it.

By Matt Burns, Vaultfish. Canonical: https://vaultfish.com/answers/can-i-sell-slack-connect-or-shared-channel-messages-to-ai  
Published: 2026-07-14  
Updated: 2026-10-14

## The short answer

The answer turns on the partner's rights. A shared-channel export carries the partner's messages, and Slack says those follow the partner's retention rules. Slack's help page doesn't say who may license them. Ask counsel whether your partner contracts and NDAs allow this use.

Shared channels are where your archive stops being only yours. Most people forget they exist.

## What does Slack say about shared-channel data?

[Slack's help page on Slack Connect](https://slack.com/help/articles/115004152843-How-data-management-features-apply-to-Slack-Connect) says "your workspace or Enterprise organization's retention settings will only apply to messages and files sent by your members." Content from outside people follows their own organization's retention policies.

Paid-plan workspace owners and admins can export data from public channels shared with other companies. The page doesn't address who owns shared-channel content.

## Does Teams handle it differently?

[Microsoft's shared channels page](https://learn.microsoft.com/en-us/microsoftteams/shared-channels) says shared channel messages are stored in a dedicated system mailbox. It says channels inherit retention, data-loss-prevention and compliance policies from the team or host organization.

It also says admins can discover all message data in the channel regardless of who added it.

That tells you who can search and export the data. It says nothing about who may license it.

## What is the risk?

A shared channel often holds a customer's, partner's or vendor's confidential information. [FKKS](https://technologylaw.fkks.com/post/102o455/selling-company-data-for-ai-training-what-to-know-before-you-say-yes) says email and chat contain other companies' confidential information. NDAs often cover it.

See [NDAs and a data license](/answers/does-my-nda-let-me-sell-data-to-ai). If the export route is an app, [Slack's API terms](https://slack.com/terms-of-service/api) (its rules for app connections) add limits. They are covered in [licensing company Slack data](/answers/is-it-legal-to-sell-company-slack-data).

I found no case about licensing shared-channel content.

## How do you sort your own messages from a partner's?

Our readiness checklist tags each system and channel in one of three ways:

- First-party.
- Held for someone else.
- Third-party content, such as Slack Connect, shared drives and guests.

We record the tags as facts. We leave the decision on third-party content to counsel.

Do that sort first. A licensing file that mixes the three groups can't show which messages you had the right to license.

Talk to a commercial lawyer in your state before you sign. The [rights check](/rights-check) asks whose records these are and whether staff messages are included.

Figure: comparison of Whose messages sit in a shared-channel export: Your members (Your retention rules), Partner's members (emphasized: Their messages keep their rules, Their own rules). Retention follows each organization's members, so a partner's messages in your export keep the partner's rules.

_Vaultfish helps you run the process. We are not lawyers and this is not legal advice. If you need counsel who knows this area, we can point you to one._

## Sources

- [Slack's help page on Slack Connect](https://slack.com/help/articles/115004152843-How-data-management-features-apply-to-Slack-Connect)
- [Microsoft's shared channels page](https://learn.microsoft.com/en-us/microsoftteams/shared-channels)
- [FKKS](https://technologylaw.fkks.com/post/102o455/selling-company-data-for-ai-training-what-to-know-before-you-say-yes)
- [Slack's API terms](https://slack.com/terms-of-service/api)