Environment

• Ruby 2.4.5
• Rails 4.2.11
• Devise 4.6.1

Current behavior

Devise is sending the "Email Changed" email when a user first signs up. This email is unnecessary because they haven't confirmed this email yet.

GIF showing both "confirmation" email AND "email changed" email.

![Double Email Gif](https://user-images.githubusercontent.com/6728265/54702757-c90f

This isn't a code-related issue, but a request to clarify email confirmation flows and endpoints in the documentation. I'd be happy to submit a pull request for this, but I need more information about how this is expected to work, before I'll be able to explain it. There's also related code that's been merged but not released yet (specifically: https://github.com/lynndylanhurley/devise_token_auth/

When I would like to use Simple Token Authentication
But the gem doesn't quite fit my use case
I want be told about alternatives
So that I can understand the trade-offs that were made
And decide if I prefer creating a pull request or use another of the tools that are available

When I maintain a gem that provides token authentication using Devise
I want t

Our continuous integration was blocked until death in setup because of the prompt for the admin user.
I had the hardest time finding how to auto accept and luckily I ended up there:
https://github.com/spree/spree_auth_devise/blob/a141130b44bcab17f8c23b7201952399b177321b/db/default/users.rb#L37

Is there some documentation that I missed about the necessity of this variable for automating the app se

The following part of the README:

The [Devise README](https://github.com/plataformatec/devise#activejob-integration) describes how to use ActiveJob to deliver emails in the background. Normally you would place the following code in your `User` model, however when using _devise-multi_email_ you should place this in the `Email` model.

does not seem to be correct. If I put the method