Answers.Body: <p>Solved this by</p>
  
  <ul>
  <li>creating the <a href="https://craftcms.com/docs/templating/set-password-form" rel="nofollow">Set Password form</a> in a template with the correct
  return</li>
  <li>setting it's path with <a href="https://craftcms.com/docs/config-settings#setPasswordPath" rel="nofollow">setPasswordPath</a>  </li>
  <li>setting a path for    <a href="https://craftcms.com/docs/config-settings#setPasswordSuccessPath" rel="nofollow">setPasswordSuccessPath</a> to catch <em>forgot password</em>
  resets</li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-16T17:40:14.297Z
Answers.LastActivityDate: 2016-03-16T17:40:14.297Z
Answers.UserDisplayName: Christy Collins
Answers.Body: <p>The currently logic around that is "if the account has Access the CP permissions, send them to the control panel login page, otherwise, send them to wherever the <code>activateAccountSuccessPath</code> config setting is set to".</p>
  
  <p>Since you've got <code>autoLoginAfterAccountActivation</code> set, the CP login page redirects to the CP dashboard.</p>
  
  <p>If that's not the behavior you're looking for, you can create a plugin that mimics the necessary <code>craft/app/controllers/UsersControllers</code> methods changing the logic for your requirements as necessary.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-16T17:43:31.987Z
Answers.Text: Thanks Brad. This member group didn't have CP access. Seems like they should have gone to activateAccountSuccessPath - but they weren't. I x-posted with you what worked for me, it's probably better to deliver my own form anyway.
Answers.UserDisplayName: Christy Collins
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-16T17:37:34.663Z
Answers.LastActivityDate: 2016-03-16T17:37:34.663Z
Answers.UserDisplayName: Brad Bell
Body: <p>When I add a new user in the admin area, they get a link to activate their account. On the screen that link goes to, they are prompted to set a password. After the password is submitted, they are returned to <code>/dashboard</code>. How do I alter that return? I have the following config variables set </p>
  
  <pre><code>'useEmailAsUsername' =&gt; true,
  'autoLoginAfterAccountActivation' =&gt; true,
  'activateAccountSuccessPath' =&gt; 'members/index',
  </code></pre>
  
Tags: <users><config>
Title: Set return URL after password is set
ThreadText: # Set return URL after password is set
  
  (Asked by: username_0 on 2016-03-16)
  
  When I add a new user in the admin area, they get a link to activate their account. On the screen that link goes to, they are prompted to set a password. After the password is submitted, they are returned to `/dashboard`. How do I alter that return? I have the following config variables set
  
  ```
  'useEmailAsUsername' => true,
  'autoLoginAfterAccountActivation' => true,
  'activateAccountSuccessPath' => 'members/index',
  
  ```
  
  **Tags:** users, config
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2016-03-16. Score: 3
  
  Solved this by
  
  * creating the [Set Password form](https://craftcms.com/docs/templating/set-password-form) in a template with the correct
    return
  * setting it's path with [setPasswordPath](https://craftcms.com/docs/config-settings#setPasswordPath)
  * setting a path for [setPasswordSuccessPath](https://craftcms.com/docs/config-settings#setPasswordSuccessPath) to catch *forgot password*
    resets
  
  
  ---
  
  ### Answer by username_1 on 2016-03-16. Score: 0
  
  The currently logic around that is "if the account has Access the CP permissions, send them to the control panel login page, otherwise, send them to wherever the `activateAccountSuccessPath` config setting is set to".
  
  Since you've got `autoLoginAfterAccountActivation` set, the CP login page redirects to the CP dashboard.
  
  If that's not the behavior you're looking for, you can create a plugin that mimics the necessary `craft/app/controllers/UsersControllers` methods changing the logic for your requirements as necessary.
  
  > **Comments:**
  > **username_0**: Thanks username_1. This member group didn't have CP access. Seems like they should have gone to activateAccountSuccessPath - but they weren't. I x-posted with you what worked for me, it's probably better to deliver my own form anyway.  
  
  ---
  
  