Please allow Slack event subscriptions and required OAuth scopes to be updated on an existing Vercel Connect connector.

Today, adding an event such as message.groups requires creating a new connector, which creates a new Slack bot. The new bot must then be invited to every private channel again, and its bot identity and mention name may change. This makes a small event-subscription change unnecessarily disruptive, especially for bots already deployed across multiple private channels.

Slack itself supports updating event subscriptions on an existing app and reauthorizing the same app when additional scopes are required. Vercel Connect should expose an equivalent update-and-reauthorize flow so the existing Slack app, bot identity, and channel memberships can be preserved.