gistfile1.rb

    context "current user exists, user is not currently using this application" do
      # Redirects to Application > Email Addresses, prompts to activate application
    end

    context "current user exists, user is currently using this application" do
      # Redirects to Application > (root)
    end

    context "no current user, EEA doesn't exist (8L)" do
     # Redirects to account_to_found 
    end

    context "no current user, EEA exists, EEA doesn't use any applications, EEA has never used this application (11L)" do
      # Redirects to Application > Email Addresses, prompts to activate application for EEA
    end

    context "no current user, EEA exists, EEA doesn't use any applications, EEA has used this application (10L)" do
      # Redirects to Application > Email Addresses, prompts to reactivate application for EEA
    end

    context "no current user, EEA exists, EEA uses an application, EEA has never used this application(9L)" do
      # Redirects to Application > Email Addresses, prompts to activate application for EEA
    end

    context "no current user, EEA exists, EEA uses an application, EEA has used this application, EEA is not currently using this application (13L)" do
      # Redirects to Application > Email Addresses, prompts to activate application for EEA
    end
   
    context "no current user, EEA exists, EEA uses an application, EEA has used this application, EEA is currently using this application (12L)" do
      # Redirects to Application > (root)
    end
 

Line 10 - What is account_to_found?

Line 13 & 17 - In these scenarios, the user has no active applications at all. Can they simply log in and click a button to reactive? Or, do they need to "sign up" and be kicked back to Gmail/Ymail?

Line 26 - I think this should be reactivate application, since the user has used it before.

that should have been account_not_found, which is an empty page saying "Hey, we don't know who this person is, maybe you should sign up" or something similar.

Good point re: 13 & 17. If we're destroying users credentials after they deactivate all their apps we'll need to go though the signup flow, but if not, we can just turn the app back on. We should chat with Alex about our policies regarding credential retention.

You're right about 26 - updated.

Pretty certain we are destroying creds after the user deactivates all their apps. We may even be destroying user accounts at some point (soon).

(my preference would be not retain credentials forever and just stop syncing accounts when users click 'Remove')

As far as I can tell we're not deleting credentials during deactivation, but I could be missing it