Change owner of cloud document
A member of our team is leaving. The only way we can change ownership of her files is to have her download them and share them locally. This is fine and all but it breaks all the links to the document so I have to go into the various places we share the link, like JIRA, and add new links.
I would prefer that we could just change ownership of the file to another team member.
Yes, this should be possible to be done from the central online storage.
Guthrie Watson commented
Designers come and go and our licenses get reassigned which is a killer because I basically have to save a whole new version in order to publish links.
Please find a way to have shared overship or transfer ownership more seamless.
Overflow.io allow you to delete users and reassign all their documents to another user in single step.
I've always recommended the Adobe products as reliable and efficient. Now is the fist time I'm seriously considering to change the tool. The fact that when document is opened from another account all links created by owner are lost/not visible/not editable is huge issue for us. Our design team is growing and now we have to choose whether to have scattered links between different accounts for the same document (for sure not an option) or to have one person creating all links for the rest of the team (also not long term solution for us). I really don't understand how this happened - the most logical thing is the links to be attached to a document not an account. We already have found a product that will save us all this pain. Hope we won't need to change the tool but for sure if we don't see your good intention to solve this issue soon we will have no other choice.
Please we need this ASAP because otherwise collaborative work with cloud documents is not possible in a big agency with many designers.
Howwwwwwww has this been sat upon for over a year Adobe?????
Guys If my email id in the account is changed to the email Id of new comer who will take over my work does this solve the issue? the links will remain same and as it is and we don't need to re export or replace XD links? let me know if this is possible? Obviously, this is only when u are leaving a Co and someone else is taking over your work. Doesn't still change the multiple owner and team management issue!
Breno Gregório Angelotti commented
The need for this is very critical and simple to explain: I'm moving to a different company, my fellow designer needs to keep the work we have done together
Jodi Bennett commented
ABSOLUTELY CRITICAL! I have needed this now THREE times in the past year! I work with a lot of Contractors so collaborators come and go quite regularly. I need to be able to not only add them as collaborators, but to assign them permissions which would include something akin to Admin rights so they can update existing URLs and become owners or whatever. I have a file that I absolutely cannot move because there is so much documentation on it in the form of comments that would be lost if I moved it from one account to another. The owner needs changing so they can get it off their computer and move on.
Such a pain in the ass when multiple designers work on the same project at different times and have to ask the person who started the project to update the link! What about when someone quits or is on vacation? Creating a new link erases all the comments which we use as a documentation also, to easily access all in one place. This is such a fundamental flaw to not be able to share the ownership.
Especially challenging when coordinating between onshore/offshore team members. This is critical for us!
Agree with everything said. I'd like to add that our team would like to co-own a file, or define a team that owns the file, so all of us can update the links to share. Right now, if someone is out, we have to wait for them to come back, or create a new link and share it out with all the stakeholders - which is a pain.
Yet another strong agreement here - lack of ownership options and the inability to update links unless you own the XD file are hard on my team workflow. When designers leave, it's a pain to organize all their content.
Anne Richardson commented
Agreed - I started at my company as a freelancer and was using my CC account. Now I'm on the company's CC account, and have to sign in and out several times a day. Sharing the doc with myself didn't give me the ability to update the same link, or transfer ownership. This is a real time-waster.
Sean Alderdice commented
This is a problem we have everyday, designers on the team do not feel empowered when they have to ask an equal to share the designs for them, this is a blocker on a daily bases
Aleksi Martikainen commented
We have exactly this same problem in our team and it really, really sucks!
Please prioritize fix for this as soon as possible so that users are able to change ownership of cloud documents. Thanks.
OR what if files could be flagged as being owned by the ACCOUNT, or even a User Group and not necessarily a specific user? So the "Design Team" could own the master cloud files regardless of which designer created it or most recently worked on it.
why can't I change or add owners to the XD document?
why I have to ask the owner to update link every time I edit the document, not having the possibility to update it myself???
why? why? whyyyyyyyyy????
Michael C commented
We are a team of 7 and had a designer move on to another job. I have to go in and open 50+ cloud files and save as a new version so someone else can publish. Now all links to existing prototypes are broken. Such a colossal waste of our time. For all the collaboration hype at Adobe Max 2020, anyone part of a UX team of 3+ designers struggles with glaring omissions such as this BASIC feature! I suppose if no one took any vacation, holiday, or sick leave and stayed with their companies for ever, this would not be an issue.
How on earth is this still not a thing?!!!?
James Wagstaff commented
Yeah - this is really needed. Co-editing is fantastic, but when you have three people working on one design and the owner goes on holiday or is moved to another project, everything falls apart. Please fix this.