title: MVC beginner - Advice on how to persist a user selection for use throughout the site
body: <p>I have an application which is centered around data per 'team'.  A user belongs to a team and if they log in they only see that team's data.</p>
  
  <p>However,  I now have super users who essentially belong to more than one team.  These users should be able to log in to the system and then immediately choose which team they are interested in.  From then on they will essentially view/create data against that selected team. They should also have the option to go and change what team they are viewing at any time.</p>
  
  <p>I've established that the user would like to be able to have multiple tabs open and be viewing a different team in each tab. </p>
  
  <p>I'm struggling to work out the best way to accomplish this with .NET MVC while keeping it as stateless and testable as possible.</p>
  
  <p>I've been reading up on the different ways to persist data - session state and cookies seem to get a bad rep in MVC.  TempData, ViewBag seem to focus on just persisting data for one request. </p>
  
  <p>I wouldn't have thought that this is an uncommon requirement in an application - are there known patterns for dealing with this in MVC which I have missed?</p>
  
  <p>So far I'm trying to create a partial view which I can show on each page to let the user see what team they are viewing the site as, and change it from there.</p>
  
  <p>Any advice is appreciated!</p>