Summary

  • An organisation’s retention settings apply to content sent by its own members. External contributions follow their sending organisation’s settings, within the same shared conversation.
  • Pinned and saved content remains subject to retention. Invitation permissions, plan exceptions and approved export scope determine the practical tools available for keeping a usable project record.

A supplier’s clarification, a revised specification and a customer’s acceptance can sit comfortably in one Slack Connect channel. Someone taking over the project later may need the explanation between them as much as the final answer. The screen offers a continuous conversation; keeping that working memory involves several organisations.

Slack’s data-management guide draws the boundary around the sender. A workspace or Enterprise organisation’s retention settings apply to messages and files, including canvases and lists, sent by its own members. External content is retained or deleted according to the settings of the organisation that sent it.

Choosing long retention for your side leaves that dependency on the other side’s contributions. If the channel becomes the project’s only memory, the buyer needs to account for it. The convenience bought today should survive a handover without returning as tomorrow’s bill for reconstructing the conversation.

The channel owner holds some important doors

The Slack Connect guide assigns ownership to the organisation in whose workspace or Enterprise organisation a channel was created. That organisation can invite and remove organisations, manage posting permissions and continue using the channel after external organisations are removed or disconnected.

Message editing and deletion have a different scope. An organisation’s settings apply to messages sent by its members. A message can only be edited or deleted by someone from its sending organisation, subject to the applicable permissions and settings. Running the room and administering every sentence inside it are distinct jobs.

Enterprise Key Management also follows content origin. An organisation’s keys encrypt messages and files sent by its members. External contributions may use the other organisation’s keys if it is also an EKM customer. The common reading surface brings those contributions together while leaving particular controls attached to their source.

The invitation matters when the work ends

Slack’s invitation-permissions documentation distinguishes permission only to post from permission to post, invite and more. The broader version includes setting a retention policy. Its table notes that this change applies to the workspace where it is made, rather than changing other organisations’ settings.

For external people invited only to post, the data guide says only the inviting organisation can set a custom retention policy for that channel. Being present in a conversation and receiving its administrative tools are separate permissions to establish.

The same guide excludes message and file data from disconnected channels where the external organisation had permission only to post. The invitation mode belongs in the understanding of how the working relationship will close. Discovering it when an old conversation is urgently needed adds an avoidable piece of administration.

A pin has no bargaining power

Slack’s retention documentation includes pinned and saved content within the policy’s reach. The pin identifies what a reader values. It gets no additional vote on the supplier’s settings.

Paid plans keep data for the lifetime of the workspace by default, with custom periods available for automatic deletion. Deletions run once a day. Organisation policies, workspace settings and permitted conversation overrides have their own conditions and responsible roles.

The case of free teams invited by an Enterprise organisation adds a specific exception. With one-year retention selected, the relevant Slack Connect channels are excepted from deletion of messages and files older than a year. With 90-day retention selected, messages and files are deleted from all channels after 90 days. The word free cannot supply one expiry date for every shared history.

For a buyer relying on the conversation, these are operating inputs. The effective setting matters more than a remembered summary of a plan page.

Inspect what the export actually supplies

The data guide allows owners and administrators of paid workspaces to export shared public channels. Extending coverage to private channels and external DMs involves the application and enabling routes for Business+ and Enterprise. The export guide separates plan, role and scope.

Included data covers external members’ messages and display names, along with links to files uploaded by members of the exporting organisation. The other company’s custom retention settings affect what appears in your export. Receiving a file link still leaves a concrete check of the material needed for the work.

Some approved configurations can remove messages from the channel view while keeping them accessible in JSON exports. Define the required working record, then inspect the permitted route that supplies it. The visible conversation and an authorised output can show different states of the content.

Assessing a particular conversation needs its sending organisations, effective retention policies, invitation permissions and approved export scope. Those inputs can support an agreed reference record, location and responsible recipient. A useful collaboration purchase carries the decisions into the next person’s work, instead of leaving that person to assemble their meaning again.