# \[Feature Request\] ACL Rules based on Tables and on columns

**URL:** <https://community.nocodb.com/t/feature-request-acl-rules-based-on-tables-and-on-columns/1951>\
**Category:** Uncategorized\
**Created:** [June 20, 2025, 12:41pm UTC](https://community.nocodb.com/t/feature-request-acl-rules-based-on-tables-and-on-columns/1951 "2025-06-20T12:41:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![fendle](https://avatars.discourse-cdn.com/v4/letter/f/c5a1d2/32.png) [@fendle](https://community.nocodb.com/u/fendle)\
**Post date:** [June 20, 2025, 12:41pm UTC](https://community.nocodb.com/t/feature-request-acl-rules-based-on-tables-and-on-columns/1951/1 "2025-06-20T12:41:09Z")

</div>

Hi,

it would be great, if we could define ACL as well based on Tables. That for example an user is for 1 table within the base an editor and in another one only viewer.

Additionally it would be good, if I could define on columns as well if it’s read only or as well writable. For example should be some fields only filled by API and not by the user

---

<div class="post-metadata">

**Author:** ![dstala](https://avatars.discourse-cdn.com/v4/letter/d/f04885/32.png) [@dstala](https://community.nocodb.com/u/dstala)\
**Post date:** [June 23, 2025, 4:36am UTC](https://community.nocodb.com/t/feature-request-acl-rules-based-on-tables-and-on-columns/1951/2 "2025-06-23T04:36:58Z")

</div>

You can track the feature request here

> <https://github.com/nocodb/nocodb/issues/9749>
>
> \### Please confirm that the feature request does \*\*\*not\*\*\* already exist
> 
> \- \[X\] …I confirm there is no existing issue for this feature request.
> 
> \### Use case
> 
> Provision granular access control for table, view & fields
> 
> \### Suggested solution
> 
> TBD
> 
> \### Additional context
> 
> \_No response\_

We do have plans to introduce table & field permissions soon as an enterprise feature.