Scenario:
- if you sent a invite to a user as a Observer, you can no longer have them participate as a guest in case it that person role change. Example, a client was intended to just be a viewer, but later it was identified that comment-role or update to fields are needed and dont need access to other things as a viewer to any workspace.
Issue:
- observers are tagged with their emails. The Observer account cannot untag himself or delete a fibery account. The IT admin/Owner of the entire workspace have NO means to migrate a user from Observer to Guest, and vice versa.
- We cannot do a request all the time to ask for fibery ticket just for the dev to do manual update on these status on the DB. It is not practical to for the support, dev, and fibery clients.