# Advanced permission rules based on field values 🔒

**URL:** <https://community.noloco.io/t/advanced-permission-rules-based-on-field-values/44>\
**Category:** Product Updates 🆕\
**Created:** [November 29, 2023, 9:24am UTC](https://community.noloco.io/t/advanced-permission-rules-based-on-field-values/44 "2023-11-29T09:24:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gill](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/gill/32/9_2.png) [@gill](https://community.noloco.io/u/gill)\
**Post date:** [November 29, 2023, 9:24am UTC](https://community.noloco.io/t/advanced-permission-rules-based-on-field-values/44/1 "2023-11-29T09:24:01Z")

</div>

Up until now, you’ve only been able to set record-level permissions based on relationship fields. In other words, you could control which records a user could access as long as the user record had a direct relationship with the relevant collection of records (e.g. a list of properties linked to the user).‍Now, you can build rules based on record field values as well! Plus, you can now write complex rules with and/or branching to set multiple conditions to control record access.‍As an example, you can now build an applicant tracking system where a user can only access applicant records where their manager is the hiring manager and if the application is still in progress based on a single option status field.