# Dec 7, 2023 / 🎄 Find References in text using AI, Custom access templates, Add many entities to Whiteboard **URL:** \ **Category:** Changelog\ **Created:** [December 7, 2023, 2:12pm UTC](https://community.fibery.io/t/dec-7-2023-find-references-in-text-using-ai-custom-access-templates-add-many-entities-to-whiteboard/5500 "2023-12-07T14:12:08Z")\ **Posts on this page:** 1\ **Showing post:** 16
**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\ **Post date:** [January 2, 2024, 2:08am UTC](https://community.fibery.io/t/dec-7-2023-find-references-in-text-using-ai-custom-access-templates-add-many-entities-to-whiteboard/5500/16 "2024-01-02T02:08:00Z")
I’m a bit confused about what a “path/level” is in the context of the custom access templates. Could you help explain how they work a little more @mdubakov or @Chr1sG? We have a lot of many-to-many related entities, so if the entity is set to “view” under one relationship and “view” & “update” under the another, what implications goes that have? Do “update” permissions simply relate to changing the relationship between entities, or does it cover updating other fields in the entity itself? Admittingly, I might be getting things confused with [entity-level permissions](https://community.fibery.io/t/in-dev-entity-level-permissions/2163) so I appreciate anything you can do to clarify. --- _[View the full topic](https://community.fibery.io/t/dec-7-2023-find-references-in-text-using-ai-custom-access-templates-add-many-entities-to-whiteboard/5500)._