# Replace Sharing Functions with a Sharing Field **URL:** \ **Category:** Ideas & Features\ **Created:** [February 21, 2025, 11:04am UTC](https://community.fibery.io/t/replace-sharing-functions-with-a-sharing-field/8303 "2025-02-21T11:04:13Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [February 21, 2025, 11:42am UTC](https://community.fibery.io/t/replace-sharing-functions-with-a-sharing-field/8303/2 "2025-02-21T11:42:44Z")
> [@RonMakesSystems](#): > > I propose remove the manual sharing completely and users can create a “Share with” field. (Ideally a polyamourous relationship with both Users and Groups, but for now could be different fields). This will make sure we don’t forget to unadd someone, easily see everything a user has access to, and doesnt risk mismatch of data. Again, not sure how helpful this really is, but just toying with the idea of really just having Entities, Fields, Views, and Reports. Nice idea, but I don’t think this would be scalable. Imagine you want to share an entity with Alice (as an Editor) with Bob (as a Viewer) and with Charles (as a Commenter). It would seem that you would need to set up a field for each possible access level. And given that there are options for custom access templates, this could become unworkable/painful. Of course, if [relationships had attributes](https://community.fibery.io/t/relationship-properties/887/9), I could imagine a ‘shared with’ collection field where you can add users, but also specify the nature of the sharing for each user, as a property of the relation. Unfortunately, I think it’s a long way away… --- _[View the full topic](https://community.fibery.io/t/replace-sharing-functions-with-a-sharing-field/8303)._