# Field Level Security

**URL:** <https://forum.mautic.org/t/field-level-security/26537>\
**Category:** Ideas and Feature Requests\
**Tags:** contacts-and-fields, user-interface, security\
**Created:** [December 28, 2022, 5:48pm UTC](https://forum.mautic.org/t/field-level-security/26537 "2022-12-28T17:48:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![marc.beinder](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/marc.beinder/32/7256_2.png) [@marc.beinder](https://forum.mautic.org/u/marc.beinder)\
**Post date:** [December 28, 2022, 5:48pm UTC](https://forum.mautic.org/t/field-level-security/26537/1 "2022-12-28T17:48:29Z")

</div>

Are there any plans to implement field level security within Mautic? I have certain fields that are populated from HubSpot and other system that are used for integration purposes.

These fields are system IDs and other system generated values that a user should not be able to edit. However, they are necessary to have in Mautic for segmentation reasons.

What I would love to see is some type of ACL where unless the roll explicitly gives the user access to edit that field, the field I hidden.

Does anyone else think that this would be useful?