Skip to content

docs: update e1-4-using-light-with-slack-and-teams.md#240

Open
habib424 wants to merge 1 commit into
mainfrom
lightship/16-employee-e1-getting-started-e1-4-using-light-with-slack-and-teams-2026-06-10
Open

docs: update e1-4-using-light-with-slack-and-teams.md#240
habib424 wants to merge 1 commit into
mainfrom
lightship/16-employee-e1-getting-started-e1-4-using-light-with-slack-and-teams-2026-06-10

Conversation

@habib424

Copy link
Copy Markdown
Collaborator

Drafted by Ship Ship 🚢 — confidence 🟢 high

What changed

Added a new subsection documenting that users can @mention Light in Slack channels (public/private) to get threaded replies, with each thread maintaining independent conversation context for multi-user collaboration. Updated the Privacy section to clarify that channel mentions are visible to everyone in the channel, while each thread maintains its own context.

Source PRs

  • light#6935 — feat(slack): handle app_mention events with threaded replies

How to use this PR

  1. Review the diff against the existing article — focus on accuracy and customer voice.
  2. Merge if it reads well. Edit and push to this branch if it needs adjustment.
  3. Close without merging if the article doesn't actually need this update.

Once we have a track record of clean drafts, we'll graduate to auto-merge with a delay buffer. For now: human-in-the-loop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant