# Disable Camera Controls for Regulated Environments **URL:** \ **Category:** Product Suggestions\ **Tags:** feature-request\ **Created:** [April 2, 2025, 8:39am UTC](https://community.tulip.co/t/disable-camera-controls-for-regulated-environments/14305 "2025-04-02T08:39:43Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![yannick](https://avatars.discourse-cdn.com/v4/letter/y/b782af/32.png) [@yannick](https://community.tulip.co/u/yannick)\ **Post date:** [April 2, 2025, 8:39am UTC](https://community.tulip.co/t/disable-camera-controls-for-regulated-environments/14305/1 "2025-04-02T08:39:43Z")
**Description:** In regulated environments, end-users must not have the ability to modify camera settings such as flipping, mirroring, resizing, or repositioning the camera view. These manipulations can compromise compliance, especially in use cases where the distance and angle to the object must remain constant (e.g., in standardized inspections or controlled visual documentation). **Requested Feature:** Add a configuration option to **lock or disable all camera manipulation controls** , including: - Flipping or mirroring the camera image - Zooming in or out - Resizing or moving the camera feed window - Changing the camera angle **Use Case:** This is critical in regulated settings (e.g., pharmaceutical, laboratory, or quality assurance workflows) where image consistency and positioning must remain fixed to comply with standard operating procedures. ---
**Author:** ![yannick](https://avatars.discourse-cdn.com/v4/letter/y/b782af/32.png) [@yannick](https://community.tulip.co/u/yannick)\ **Post date:** [April 2, 2025, 8:42am UTC](https://community.tulip.co/t/disable-camera-controls-for-regulated-environments/14305/2 "2025-04-02T08:42:55Z")
![captured image](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/a/a7ec29f8fe4944c78e20e4d8f97ba30d1886c16a.png) ---
**Author:** ![shep](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/shep/32/8231_2.png) [@shep](https://community.tulip.co/u/shep)\ **Post date:** [April 14, 2025, 2:19pm UTC](https://community.tulip.co/t/disable-camera-controls-for-regulated-environments/14305/3 "2025-04-14T14:19:21Z")
Hi @yannick thanks for submitting this product suggestion! Would disabling or hiding these camera controls solve for your use case? Could you share a bit more on how this would help standardize image capture in your operating procedures? ---
**Author:** ![OlgaStroilova](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/olgastroilova/32/7199_2.png) [@OlgaStroilova](https://community.tulip.co/u/OlgaStroilova)\ **Post date:** [July 1, 2025, 1:39pm UTC](https://community.tulip.co/t/disable-camera-controls-for-regulated-environments/14305/4 "2025-07-01T13:39:52Z")
hi @yannick - would you be ok updating this configuration on a per-widget basis, or are you hoping for a site configuration? If it’s a site configuration, this would impact camera settings on _all_ widgets across all apps, not just individual ones. We were thinking that a per-widget configuration to disable camera settings would be a good place to start. Let us know what you think here. viz @Olivier ---
**Author:** ![yannick](https://avatars.discourse-cdn.com/v4/letter/y/b782af/32.png) [@yannick](https://community.tulip.co/u/yannick)\ **Post date:** [July 2, 2025, 10:32am UTC](https://community.tulip.co/t/disable-camera-controls-for-regulated-environments/14305/5 "2025-07-02T10:32:57Z")
> [@OlgaStroilova](#): > > u be ok updating this configuration on a per-widg Hello Olga, thanks for your message. Per-widget basis would be totally fine. I would imagine similar to the functionality of making the comment field hidden, required or optional in the signature widget, that you implemented recently. Best, Yannick ![image](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/8/80f972bf23333b750d97ed13cb61f4952bc3619d.png)