feat(slack): support organization-scoped shared app rollout - #7833

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Sep 15, 2026 1:04am UTC

Confidence Score: 5/5

The PR appears safe to merge; organization ownership is consistently propagated and revalidated across shared-app setup and execution paths.

Summary

This PR changes the shared Slack Search app rollout from a deployment-wide decision to an organization-scoped feature-flag decision.

• Propagates canonical organization ownership through setup, OAuth callbacks, managed personal connections, installation management, and bot execution authorization.
• Rechecks organization-specific availability at OAuth and execution lifecycle boundaries.
• Preserves global fallback behavior and keeps custom Slack apps independent of the shared-app rollout.
• Adds focused tests for organization allowlisting, withdrawal of access, OAuth state handling, and execution reauthorization.

sequenceDiagram
  participant Admin
  participant Setup as Slack Setup
  participant Flag as Feature Flags
  participant Slack
  participant DB
  participant Worker as Bot Worker

  Admin->>Setup: Start shared-app setup for organization
  Setup->>Flag: Check shared app with orgId
  Flag-->>Setup: Organization enabled
  Setup->>Slack: Begin OAuth
  Slack-->>Setup: OAuth callback
  Setup->>Flag: Recheck with owning orgId
  Setup->>DB: Persist installation and credential
  Slack->>Worker: Deliver event
  Worker->>DB: Load installation and owning organization
  Worker->>Flag: Recheck shared app with installation orgId
  Flag-->>Worker: Enabled or denied
  Worker->>Slack: Execute bot response when enabled

_{Reviews (1) · Last reviewed commit: "feat(slack): support organization-scoped..."}