Answers.Body: <p>Look at your User Role and Access Permissions. Do you have access to CiviCRM: administer payment processors 
  Add, Update, or Disable Payment Processors ???</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-10-25T20:18:47.700Z
Answers.LastActivityDate: 2017-10-25T20:18:47.700Z
Answers.UserDisplayName: Iowa Boy
Answers.Body: <p>I just confirmed all is well in 4.7.25 -> I can edit/save the civicrm/admin/contribute/iatssettings form and all is there on refresh. </p>
  
  <p>I generally recommend updating to 4.7.25 - from a payment processing point of view our test-matrix transactions grid has never been that green;</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-10-26T02:19:40.760Z
Answers.Text: Okay. I will try updating to 4.7.25 to see if that resolves the issue.
Answers.UserDisplayName: John Richardson
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-10-26T00:59:42.337Z
Answers.LastActivityDate: 2017-10-26T00:59:42.337Z
Answers.UserDisplayName: KarinG - Semper IT
Body: <p>I am running Civi 4.7.22 and iatspayments ext 1.6.1. When I try to edit the settings (Admin>Civicontribute>iATS Payment Settings) my edits won't stick. For instance, I try to edit the email address for notification on failed recurring transactions and submit, but when refreshed the page reverts to previous email settings. Same thing with editing the "Never" to "Always" for receipts.</p>
  
  <p>Anyone with same problem, suggested solutions or troubleshooting thoughts?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-10-25T20:02:52.670Z
Comments.Text: Does your IATS user id end in 01 or 80?
Comments.UserDisplayName: Tommy B
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-10-26T01:02:52.827Z
Comments.Text: I always recommend to use 01 as your admin accounts; and ensure only 01  (02 03 etc) have refund capabilities; use your 80, 81, 82 etc as website deposit accounts (ensure they have no refund capabilities - contact iATS Customer Service to set that up); that way even if your site gets hacked - or in case of the disgruntled employee scenario - no-one can log into iATSpayments.com and refund your contributions;
Comments.UserDisplayName: KarinG - Semper IT
Tags: <civicontribute><iats>
Title: Why can't I edit iATS Settings?
ThreadText: # Why can't I edit iATS Settings?
  
  (Asked by: username_0 on 2017-10-25)
  
  I am running Civi 4.7.22 and iatspayments ext 1.6.1. When I try to edit the settings (Admin>Civicontribute>iATS Payment Settings) my edits won't stick. For instance, I try to edit the email address for notification on failed recurring transactions and submit, but when refreshed the page reverts to previous email settings. Same thing with editing the "Never" to "Always" for receipts.
  
  Anyone with same problem, suggested solutions or troubleshooting thoughts?
  
  **Tags:** civicontribute, iats
  
  > **Comments:**
  > **username_1**: Does your IATS user id end in 01 or 80?  
  > **username_2**: I always recommend to use 01 as your admin accounts; and ensure only 01  (02 03 etc) have refund capabilities; use your 80, 81, 82 etc as website deposit accounts (ensure they have no refund capabilities - contact iATS Customer Service to set that up); that way even if your site gets hacked - or in case of the disgruntled employee scenario - no-one can log into iATSpayments.com and refund your contributions;  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_3 on 2017-10-25. Score: 1
  
  Look at your User Role and Access Permissions. Do you have access to CiviCRM: administer payment processors
  Add, Update, or Disable Payment Processors ???
  
  
  ---
  
  ### Answer by username_2 on 2017-10-26. Score: 1
  
  I just confirmed all is well in 4.7.25 -> I can edit/save the civicrm/admin/contribute/iatssettings form and all is there on refresh.
  
  I generally recommend updating to 4.7.25 - from a payment processing point of view our test-matrix transactions grid has never been that green;
  
  > **Comments:**
  > **username_0**: Okay. I will try updating to 4.7.25 to see if that resolves the issue.  
  
  ---
  
  