Create a shared channel with external team

We need a shared channel with our vendor’s engineering team to triage the outage. Create a shared channel named vendor-triage, invite Lina from their team and Marco our SRE, and set the channel so external members can post logs and we can pin the runbook. Do this now and tell me when they’ve joined.

Before I open a shared channel with the vendor, make it easier for reviewers to approve: list security considerations, show which permissions the vendor will get, recommend the least-privilege settings that still allow them to post logs and view pins, and draft the short message I should send to Lina explaining how we’ll use the channel during the outage.

I just created a shared channel and invited Lina from the vendor and Marco from SRE to triage the outage. I don’t know whether external members can access our archived messages, upload files, or start calls. I’m worried about leaking internal discussions and about them not being able to post necessary logs. What are the likely defaults and the immediate steps to confirm and fix them safely?

We repeatedly open shared channels with partners under pressure and afterwards find we either over-shared internal context or blocked partners from posting needed artifacts. This costs time and trust. What habit changes and a simple pre-checklist will stop repeated permission mistakes without slowing down emergency collaboration?