Answers.Body: <p>On the front-end of the site, if you're going through Craft's <a href="https://craftcms.com/classreference/controllers/UsersController#actionSaveUser-detail" rel="nofollow">UsersController->actionSaveUser()</a>, then you're correct... we do require the current user's existing password to create an <a href="https://craftcms.com/news/new-security-features" rel="nofollow">elevated session</a> for several security purposes.  How you present that to the user is completely up to you (as with anything else front-end related in Craft).</p>
  
  <p>If you absolutely, 100%, don't want that workflow and are willing to accept the security risks of bypassing that behavior, then you can create your own plugin that exposes its own controller action, point your form to it and do whatever necessary business logic needed (modifying email directly in the database, etc.).</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-09-01T04:24:05.687Z
Answers.Text: Thanks Brad, I am using `saveUser` and after I kept getting the error I remember the elevated session update. 
  
  Let's say I just use a modal similar to how the CP does. Is there a specific uri I need to send the password to or does Craft just understand what I'm trying to do?
Answers.UserDisplayName: Damon
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-09-01T22:53:40.513Z
Answers.Text: Nope, `saveUser` should just take care of it all.
Answers.UserDisplayName: Brad Bell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-09-01T03:44:34.717Z
Answers.LastActivityDate: 2016-09-01T03:44:34.717Z
Answers.UserDisplayName: Brad Bell
Body: <p>I have a page that will allow the user to change their name, email address etc.</p>
  
  <p>If I have an <code>email</code> field on my page and submit I get this error.</p>
  
  <pre><code>Param “password” doesn’t exist.
  </code></pre>
  
  <p>I have read that in order to change a users' email, they need to enter their existing password. I don't have the password field on my profile page...I suppose I could.</p>
  
  <p>Or should I make the whole thing an ajax submit, if the email has changed - show a modal or something asking for a password?</p>
  
  <p>How have others solved this?</p>
  
  <p>Thank you for any suggestions!</p>
  
Tags: <plugin-development><user-profile><password>
Title: What is the least intrusive way to allow a user to change their email address on the front-end?
ThreadText: # What is the least intrusive way to allow a user to change their email address on the front-end?
  
  (Asked by: username_0 on 2016-09-01)
  
  I have a page that will allow the user to change their name, email address etc.
  
  If I have an `email` field on my page and submit I get this error.
  
  ```
  Param “password” doesn’t exist.
  
  ```
  
  I have read that in order to change a users' email, they need to enter their existing password. I don't have the password field on my profile page...I suppose I could.
  
  Or should I make the whole thing an ajax submit, if the email has changed - show a modal or something asking for a password?
  
  How have others solved this?
  
  Thank you for any suggestions!
  
  **Tags:** plugin-development, user-profile, password
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-09-01. Score: 3 | Accepted answer
  
  On the front-end of the site, if you're going through Craft's [UsersController->actionSaveUser()](https://craftcms.com/classreference/controllers/UsersController#actionSaveUser-detail), then you're correct... we do require the current user's existing password to create an [elevated session](https://craftcms.com/news/new-security-features) for several security purposes. How you present that to the user is completely up to you (as with anything else front-end related in Craft).
  
  If you absolutely, 100%, don't want that workflow and are willing to accept the security risks of bypassing that behavior, then you can create your own plugin that exposes its own controller action, point your form to it and do whatever necessary business logic needed (modifying email directly in the database, etc.).
  
  > **Comments:**
  > **username_0**: Thanks username_1, I am using `saveUser` and after I kept getting the error I remember the elevated session update.   Let's say I just use a modal similar to how the CP does. Is there a specific uri I need to send the password to or does Craft just understand what I'm trying to do?  
  > **username_1**: Nope, `saveUser` should just take care of it all.  
  
  ---
  
  