We would like to reduce a seat in the company to a guest without losing the person’s data and allowing them to keep their account. The seat is needed for another person. What is the procedure here? Can the person switch to another domain and then receive guest access when the company domain is removed?
See this topic, and my post there. Even though it’s asking for the reverse change as you, it’s the same underlying reason why you can’t make a “switch” and have to treat it as two separate logins and migrate work.
See also:
Thanks,
Larry
1 Like
Thanks @lpb,
but neither contains the definitive answer to my question. I have also created a support ticket, but was referred to the sales partner, who certainly does not know.
I will try to add another email domain to the employee’s account and remove the member email, but with the suspicion that Asana will want to create another account with it. If the latter is the case, we will then have to set up a guest account and transfer all necessary data from the member to the guest account.
Thank you very much for your help.
Hi,
I think you should push back on Support to give you a definitive answer.
In lieu of that, and with a grain of salt…
Be careful not to remove the existing account prematurely.
Invite a new email address with any domain name other than your org’s domain (so it could be gmail.com) to create the new Guest login.
Login with the domain (Member) login. For every assigned task/subtask, change the assignee to the new Guest email. Same for all places where the Member is a collaborator. Account for all other ownership (like projects, portfolios, rules, custom fields if the Member created work objects). This is not a complete list, but some more info about things to think about is at:
Login with that new Guest login and make sure everything works before deprovisioning the old Member login.
1 Like