Answers.Body: <p>There is an "<a href="http://buildwithcraft.com/docs/config-settings#allowAutoUpdates">allowAutoUpdates</a>" config setting that you can set to false, which will disable auto-updating for a Craft install.  Manual updating will still work, though.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-12T17:09:54.910Z
Answers.Text: It would be nice to see this option available to check off in the user/user group control panel. You could disallow it for everyone, including Site Admins, then go back to each individual user and allow them to run updates. This way you can allow clients the peace of mind of having a super admin account (which they could still go and undo what you just did above) while making it difficult for them to run updates and possible mess something up.
Answers.UserDisplayName: Stuart McCoy
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-12T02:03:15.117Z
Answers.LastActivityDate: 2014-06-12T02:03:15.117Z
Answers.UserDisplayName: Brad Bell
Answers.Body: <p>You can use the <code>config/general.php</code> file to specify whether auto-updating is allowed:</p>
  
  <p><strong>Craft 2</strong></p>
  
  <pre><code>'allowAutoUpdates' =&gt; false
  </code></pre>
  
  <blockquote>
    <p><a href="https://docs.craftcms.com/v2/config-settings.html#allowAutoUpdates" rel="noreferrer">https://docs.craftcms.com/v2/config-settings.html#allowAutoUpdates</a></p>
  </blockquote>
  
  <p><strong>Craft 3</strong></p>
  
  <pre><code>'allowUpdates' =&gt; false
  </code></pre>
  
  <blockquote>
    <p><a href="https://docs.craftcms.com/api/v3/craft-config-generalconfig.html#property-allowupdates" rel="noreferrer">https://docs.craftcms.com/api/v3/craft-config-generalconfig.html#property-allowupdates</a></p>
  </blockquote>
  
  <p>Combined with a multi-environment configuration, this can be very helpful.</p>
  
  <p>Admittedly, this doesn't prevent the "Updates are available" notification from appearing... There have been some discussions about future versions of Craft possibly adding a separate config setting which will allow you to disable that notification as well.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-12T02:15:06.227Z
Answers.Text: Stop making your answer better than mine!
Answers.UserDisplayName: Brad Bell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-12T02:17:13.603Z
Answers.Text: Lol... You may be overqualified to handle a question like this... Save your rep for those really complicated ones. ;)
Answers.UserDisplayName: Lindsey D
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-12T02:34:06.537Z
Answers.Text: Perfect. If I want to hide the updates badge completely I'll just use your excellent [CP CSS Plugin](https://github.com/lindseydiloreto/craft-cpcss), Lindsey ;)
Answers.UserDisplayName: Alex Kendrick
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-12T04:42:51.607Z
Answers.Text: Hadn't even thought of that! Great idea Alex!
Answers.UserDisplayName: Lindsey D
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2014-06-12T02:05:18.960Z
Answers.LastActivityDate: 2018-06-06T16:12:06.970Z
Answers.LastEditDate: 2018-06-06T16:12:06.970Z
Answers.UserDisplayName: Lindsey D
Body: <p>How can I prevent my client from auto-updating Craft in production? I don't want them to run Craft updates on the production site, but the "updates" badge seems irresistible to them. I would prefer to run Craft updates in my dev environment, version control with Git, test, and then deploy at my leisure.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-06-12T04:19:20.387Z
Comments.Text: My guess is that Craft's update badge was specifically engineered for *irresistableness*. I'm not even on the client side, and I still have to remind myself to play it cool.
Comments.UserDisplayName: Matt Stein
Tags: <auto-updates>
Title: How can I prevent my client from auto-updating Craft in production?
ThreadText: # How can I prevent my client from auto-updating Craft in production?
  
  (Asked by: username_0 on 2014-06-12)
  
  How can I prevent my client from auto-updating Craft in production? I don't want them to run Craft updates on the production site, but the "updates" badge seems irresistible to them. I would prefer to run Craft updates in my dev environment, version control with Git, test, and then deploy at my leisure.
  
  **Tags:** auto-updates
  
  > **Comments:**
  > **username_1**: My guess is that Craft's update badge was specifically engineered for *irresistableness*. I'm not even on the client side, and I still have to remind myself to play it cool.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_4 on 2014-06-12. Score: 47 | Accepted answer
  
  You can use the `config/general.php` file to specify whether auto-updating is allowed:
  
  **Craft 2**
  
  ```
  'allowAutoUpdates' => false
  
  ```
  
  > <https://docs.craftcms.com/v2/config-settings.html#allowAutoUpdates>
  
  **Craft 3**
  
  ```
  'allowUpdates' => false
  
  ```
  
  > <https://docs.craftcms.com/api/v3/craft-config-generalconfig.html#property-allowupdates>
  
  Combined with a multi-environment configuration, this can be very helpful.
  
  Admittedly, this doesn't prevent the "Updates are available" notification from appearing... There have been some discussions about future versions of Craft possibly adding a separate config setting which will allow you to disable that notification as well.
  
  > **Comments:**
  > **username_2**: Stop making your answer better than mine!  
  > **username_4**: Lol... You may be overqualified to handle a question like this... Save your rep for those really complicated ones. ;)  
  > **username_0**: Perfect. If I want to hide the updates badge completely I'll just use your excellent [CP CSS Plugin](https://github.com/lindseydiloreto/craft-cpcss), username_4 ;)  
  > **username_4**: Hadn't even thought of that! Great idea username_0!  
  
  ---
  
  ### Answer by username_2 on 2014-06-12. Score: 9
  
  There is an "[allowAutoUpdates](http://buildwithcraft.com/docs/config-settings#allowAutoUpdates)" config setting that you can set to false, which will disable auto-updating for a Craft install. Manual updating will still work, though.
  
  > **Comments:**
  > **username_3**: It would be nice to see this option available to check off in the user/user group control panel. You could disallow it for everyone, including Site Admins, then go back to each individual user and allow them to run updates. This way you can allow clients the peace of mind of having a super admin account (which they could still go and undo what you just did above) while making it difficult for them to run updates and possible mess something up.  
  
  ---
  
  