{"section":"announcements","requestedLocale":"en","requestedSlug":"2026-11-16-vtex-cx-platform-enterprise-okta-login","locale":"en","slug":"2026-11-16-vtex-cx-platform-enterprise-okta-login","path":"docs/en/announcements/2026/november/2026-11-16-vtex-cx-platform-enterprise-okta-login.md","branch":"main","content":"Enterprise clients can now log in to [VTEX CX Platform](https://help.vtex.com/en/docs/tutorials/vtex-cx-platform-visao-geral) using Okta. To meet the security requirements of companies that centralize authentication with their own identity provider, we made this feature available to all clients.\n\nWith Okta login, users log in with their corporate credentials, and two-factor authentication follows the rules already defined in the client's Okta.\n\n## What has changed?\n\nPreviously, all users logged in to the platform with email and password or with social login buttons (GitHub, Google, and Microsoft), without the option to use their own company's identity provider.\n\nNow, the login screen first asks only for the email and directs the user based on the domain provided:\n\n- **Domain mapped to an Okta tenant:** the user is redirected directly to the company's Okta, including Okta's configured MFA. The platform's password field isn't displayed in this attempt.\n- **Domain not mapped:** the user proceeds to the password step, as before.\n\nThe GitHub, Google, and Microsoft login options remain available and haven't changed.\n\n> ℹ️ Access to organizations is still granted only by invite, and domain mapping is restricted per client: one company's Okta never grants access to another organization.\n\n## What needs to be done?\n\nTo use this feature, contact [VTEX Support](https://help.vtex.com/en/support) and request the configuration of your organization's email domain mapping and policy."}