Tags | Migration |

Enterprise users can access their documentation here. Find your plan.

NOTE: if you're having problems accessing your team at the new stackoverflowteams.com URL, jump to the "Troubleshooting" section at the bottom of this article.

Introducing a new domain for Stack Overflow for Teams
To improve product experience, security, and scale, we’re separating the stackoverflow.com public site and your Stack Overflow for Teams site. This has two main benefits:

Currently, we host Stack Overflow for Teams on the stackoverflow.com domain along with our public site. To separate the sites, we're moving Teams onto its own domain dedicated to hosting Teams. All existing stackoverflow.com/c/[team_name] links will redirect to the new domain stackoverflowteams.com/c/[team_name].

This means your URL will change from stackoverflow.com/c/[your_team] to stackoverflowteams.com/c/[your_team], and private teams will no longer appear in the left sidebar on stackoverflow.com.

Bringing clarity and security to how you find answers
In addition to accessing your team through a new URL, you'll notice a refreshed look and experience on Stack Overflow for Teams. The updated interface helps visually distinguish when you're working in your private Team and when you're in the global, public Stack Overflow community.

One of the most significant changes is that you'll no longer see private teams in the left sidebar on stackoverflow.com. Instead, you'll access private teams from the new stackoverflowteams.com domain.

A new "FOR TEAMS" tile in the upper-left navigation shows when you're on the stackoverflowteams.com Teams domain. You can easily switch between your private teams using a drop-down menu located next to the search box.

Also, this release restores the Inbox button to the top of the screen for easier navigation.

Unified Search
Unified Search works across Teams and the public community site, giving Teams users a searchable, read-only index of the public site within their private teams search results. This means you can read answers from the public stackoverflow.com site when you search, but you can't post on stackoverflow.com from your private team. This ensures you and your team members benefit from the global community’s wealth of knowledge while eliminating accidental posts outside of your organization. You'll still be able to use personal stackoverflow.com accounts to engage with the global community outside of your private team.

To include results from the public site in your Teams search, check the Include results from stackoverflow.com checkbox in the search results box.

Once the migration is complete, update any existing bookmarks or workflows you have to accommodate the new URL (stackoverflowteams.com/c/[your_team]). You'll no longer be able to access your private team from the public stackoverflow.com site.

We'll begin migrations in November and finish by the end of the year. When we schedule your team’s migration, we'll notify Teams administrators with dates and details. All users will receive migration communications from Stack Overflow via email and in-application messages.

If you're unable to locate your Team at stackoverflowteams.com, or if you see the error "This email is already in use", you've likely logged into stackoverflowteams.com with the wrong email address. You need to log in to stackoverflowteams.com with the same email address you used for stackoverflow.com.

If you don't remember which email address you used, log back in to stackoverflow.com (or use a browser that's still logged in) and access https://stackoverflow.com/users/mylogins/current. Look for the email address used for your latest login.

Log out of stackoverflowteams.com, then log back in to stackoverflowteams.com using the email address you used for stackoverflow.com.

Need help? Submit an issue or question through our support portal.