# "Personal Accounts" disabled by default

Starting today for new applications, when you enable our Organizations featureset, your users will be required to create or join an organization. Previously, we defaulted to allowing a "Personal Account" which caused many of you building B2B applications to add workarounds to force organization membership. We had it backwards.

And if you're using Clerk components, this just works. Users are immediately prompted upon sign-up or sign-in.

[View video](./disabled-personal-accounts.mp4)

## Opt-in to Personal Accounts

If you'd still like Personal Accounts to exist alongside Organizations in for your application, thats still possible. Simply toggle "Enable Personal Account" at the moment you enable organization or in the [Organization settings](https://dashboard.clerk.com/~/organizations-settings) in the Clerk Dashboard.

## Migration considerations

Due to the way this could change some of the way your application handles sessions, this functionality is only available for newly created applications. If you're running an existing application and want to adopt the new default, please [contact our support team](https://clerk.com/contact/support) to discuss a migration strategy.

## Learn more

For detailed implementation guides and examples, check out our [documentation on organization-based authentication](https://clerk.com/docs/authentication/configuration/session-tasks.md).