Vercel Connect adds enterprise-managed authorization for agents
A new public beta lets agents use services such as Slack on a signed-in employee's behalf, routed through the company identity provider instead of a separate consent screen per service.
Vercel added Enterprise-Managed Authorization to Vercel Connect in public beta on 15 October. It lets an agent or app act on a signed-in employee’s behalf against services such as Slack, without showing that employee a separate consent screen for every service it touches.
Administrators grant or revoke access to services through the company’s identity provider, with Okta named as a compatible option. Vercel Connect exchanges the IdP’s refresh token for an Identity Assertion JWT Authorization Grant, then redeems that for a service access token, handling caching and renewal itself. Access stays capped at the scopes an app requests and whatever permissions the signed-in user already has. Slack’s MCP server is the example Vercel points to for wiring this into agent tool use.
Why it matters: agents built on MCP or other tool-calling setups usually hit one OAuth consent screen per service, per user. Routing that through a company’s existing identity provider instead gives IT centralised control over what an agent can reach, without every employee clicking through an authorization flow for each connected service.
The caveat: public beta, and Okta is the only identity provider Vercel names as confirmed so far.