{"slug": "vercel-connect-adds-enterprise-managed-authorization", "title": "Vercel Connect adds Enterprise-Managed Authorization", "summary": "Vercel Connect now supports Enterprise-Managed Authorization (EMA) in public beta, letting apps and agents access supported services on behalf of signed-in users without separate consent prompts per service. Administrators grant or revoke service access through the identity provider, users sign in with corporate accounts via compatible providers such as Okta, and Connect handles token exchange, caching, and renewal within approved scopes and the user's existing service permissions. Connect supports Cross-App Access (XAA), including its use for MCP authorization through EMA, and Vercel Passport users can request a token for Slack's Model Context Protocol (MCP) server with the signed-in user's identity.", "body_md": "[Vercel Connect](https://vercel.com/connect) now supports [Enterprise-Managed Authorization (EMA)](https://vercel.com/docs/connect/ema) in public beta. Your apps and agents can access supported services on behalf of signed-in users without separate consent prompts for each service.\n\nHere's how access works:\n\n**Admin-managed access:** Administrators can grant or revoke access to supported services through the identity provider.\n\n**Corporate sign-in:** Users sign into your app with their corporate account through a compatible identity provider such as [Okta](https://developer.okta.com/docs/concepts/xaa/).\n\n**Scoped tokens:** Your app requests the scopes it needs, and Connect handles token exchange, caching, and renewal. Access is limited to approved scopes and the user’s existing service permissions.\n\nIf your app uses [Vercel Passport](https://vercel.com/passport), you can request a token for [Slack’s Model Context Protocol (MCP) server](https://docs.slack.dev/authentication/enterprise-managed-authorization/) with the signed-in user’s identity:\n\ntype: embedded-entry-inline id: 1T9cFkjaRDDmRFQ5bWVmD6\n\nConnect supports [Cross-App Access (XAA)](https://datatracker.ietf.org/doc/html/draft-ietf-oauth-identity-assertion-authz-grant), including its use for MCP authorization through EMA. Follow the [Vercel Connect EMA setup guide](https://vercel.com/docs/connect/ema) to configure your identity provider and services and enable EMA on their Connect connectors.", "url": "https://wpnews.pro/news/vercel-connect-adds-enterprise-managed-authorization", "canonical_source": "https://vercel.com/changelog/vercel-connect-adds-enterprise-managed-authorization", "published_at": "2026-10-15 00:00:00+00:00", "updated_at": "2026-10-15 17:55:58.820507+00:00", "lang": "en", "topics": ["ai-agents", "agent-protocols", "developer-tools", "ai-infrastructure"], "entities": ["Vercel", "Vercel Connect", "Enterprise-Managed Authorization", "Okta", "Vercel Passport", "Slack", "Model Context Protocol", "Cross-App Access"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/vercel-connect-adds-enterprise-managed-authorization", "markdown": "https://wpnews.pro/news/vercel-connect-adds-enterprise-managed-authorization.md", "text": "https://wpnews.pro/news/vercel-connect-adds-enterprise-managed-authorization.txt", "jsonld": "https://wpnews.pro/news/vercel-connect-adds-enterprise-managed-authorization.jsonld"}}