# "Same as" relationship

**URL:** <https://community.fibery.io/t/same-as-relationship/513>\
**Category:** Ideas & Features\
**Tags:** flexible-domain\
**Created:** [January 13, 2020, 1:35am UTC](https://community.fibery.io/t/same-as-relationship/513 "2020-01-13T01:35:04Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![jean1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jean1/32/1669_2.png) [@jean1](https://community.fibery.io/u/jean1)\
**Post date:** [May 13, 2021, 5:23pm UTC](https://community.fibery.io/t/same-as-relationship/513/7 "2021-05-13T17:23:40Z")

</div>

Ah, this “Human” extension looks like the “login” trait I was proposing:

> [@Fibery users should be entities just like any other](https://community.fibery.io/t/fibery-users-should-be-entities-just-like-any-other/1518):
>
> “Can login” should be a trait or behaviour that can be added to types in Fibery. I elaborate more on how this could work at [Convert entities of one Type to another Type](https://community.fibery.io/t/convert-entities-of-one-type-to-another-type/428/5). E.g. I don’t want synced github members, and then have to manage sync between github issue assignments vs Fibery user assignments. Instead, I want to be able to select github members and allow them to log in.

---

_[View the full topic](https://community.fibery.io/t/same-as-relationship/513)._