# Enforce setting(s) across team/org

**URL:** <https://forum.cursor.com/t/enforce-setting-s-across-team-org/145028>\
**Category:** Feature Requests\
**Created:** [December 2, 2025, 3:11pm UTC](https://forum.cursor.com/t/enforce-setting-s-across-team-org/145028 "2025-12-02T15:11:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Martin\_Picard](https://avatars.discourse-cdn.com/v4/letter/m/b2d939/32.png) [@Martin\_Picard](https://forum.cursor.com/u/Martin_Picard)\
**Post date:** [December 2, 2025, 3:11pm UTC](https://forum.cursor.com/t/enforce-setting-s-across-team-org/145028/1 "2025-12-02T15:11:16Z")

</div>

### Feature request for product/service

Cursor IDE

### Describe the request

After SHA1-Hulud our organisation is discussion ways to prevent Cursor from autoupdating extensions and possibly also Cursor. If there was a way to enforce all Cursor instances in our team/organisation to have autoupdate off or extension autoupdate, that would satisfy our requirements to have time for security team to review before updating.