# Virtual or Dummy User

**URL:** <https://community.fibery.io/t/virtual-or-dummy-user/894>\
**Category:** Ideas & Features\
**Created:** [August 11, 2020, 3:35pm UTC](https://community.fibery.io/t/virtual-or-dummy-user/894 "2020-08-11T15:35:23Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**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:** [August 11, 2020, 5:21pm UTC](https://community.fibery.io/t/virtual-or-dummy-user/894/2 "2020-08-11T17:21:43Z")

</div>

Seems to share some of the issues in the ‘same as’ discussion:

> [@"Same as" relationship](https://community.fibery.io/t/same-as-relationship/513):
>
> Hi everyone, I am trying to work out what is the best way of setting up entities which represent the same thing (but with different types of detail). For example employees who are also Fibery users. At the moment, I am working on setting up the various apps and testing them myself before rolling it out to other members of our team. As time goes on and more of my team work on the system, which means some (but not all) of the employees in the Employee Management app would also be users. I would …

It would certainly be nice to have People who can be linked to other entities (assignee etc.) but aren’t fibery users and don’t add to the billing count

---

_[View the full topic](https://community.fibery.io/t/virtual-or-dummy-user/894)._
