# Ability to limit the scope of a relation

**URL:** <https://community.anytype.io/t/ability-to-limit-the-scope-of-a-relation/1553>\
**Category:** Feature Requests\
**Tags:** Properties, Product\
**Created:** [August 7, 2021, 5:14pm UTC](https://community.anytype.io/t/ability-to-limit-the-scope-of-a-relation/1553 "2021-08-07T17:14:31Z")\
**Posts on this page:** 1\
**Showing post:** 27

<div class="post-metadata">

**Author:** ![Filip](https://community.anytype.io/user_avatar/community.anytype.io/filip/32/22248_2.png) [@Filip](https://community.anytype.io/u/Filip)\
**Post date:** [May 10, 2024, 9:20am UTC](https://community.anytype.io/t/ability-to-limit-the-scope-of-a-relation/1553/27 "2024-05-10T09:20:34Z")

</div>

Extra feedback:

> [@What is your dealbreaker with Anytype?](https://community.anytype.io/t/what-is-your-dealbreaker-with-anytype/9406/93):
>
> User case : user from Notion, with multiples database. In Notion, each database has its own properties (relations) and pages (objects). In AT, a relation or an object are in AT.  
> In practice, this poses organizational problems and, with the multiplication of data, will tend to create a big “mess”.
> 
> - All relation will be visible everywhere, all the time. If you have 50 databases with dozens of relations (usually specific to the db), you’ll have a list of 500 relationships to manage (add relationship → search the list…). If a relationship has the same name in different places, too bad, the relation list will display the same name several times.
> - The same goes for objects and type (the person I spoke to gave me a nice explanation of the problem, but I forgot).  
> Hence the need to localize data that is of no interest at a global level.

---

_[View the full topic](https://community.anytype.io/t/ability-to-limit-the-scope-of-a-relation/1553)._