Coediting makes no sense if I have to still rely on the owner to update the online design specs/link. Big disappointment for many collaborative teams. We'll move to Figma by EOY if this is not addressed.

I understand it being intentional, and if so it should be al lock on the file. I can't share any file if this is a thing as the whole point of sharing with my team is so they can take over.

Why is the last update (above) on this dated Aug 25, 2017? When we all are still asking for this in October, 2019? Adobe - get with the program.

This issue was launched two years ago. Our team just decided to commit to Adobe XD for our designs and just ran into this issue with working on our first design for a client using XD. I would have expected a fix for this by now since it's been 2 years. Any chance this feature would be coming soon. We are geographically distributed team and will probably be switching to something else that has better ownership management.

This makes scaling design teams very difficult where multiple files need to be handed off to other designers. Restrictions on who can update links results in creating duplicates of link. This creates confusion within the team and for stakeholders. Especially for teams that do not use Adobe CC for housing files (internal servers).

Adobe listen to your users. This Ownership concept is bad it does not create a good workflow in a team setting. Please address this in XD.

Please add proper link management. This is very annoying when collaborating with multiple designers. At the very least: If I open the file, I should be able to select a link I own and post to that link, no matter which prototype/design spec is involved.

Having to recreate links over and over is cumbersome and confusing for your developers.

Allowing the original owner to add more owners (and those owners to add owners) would make this a more viable tool for my teams.

We have a team of 5 designers and as we move more toward using XD as our main design tool the fact that there is no other way for other designers to update existing link is really frustrating for us and stakeholders. On top of that it generates a lot of confusion and additional work with maintaining updated links across the documentation.

WE NEED THIS!!
It doesn't make sense that only the file owner can update the link.
If I want to give another user permission to update the link, it is my responsibility and decision.
This is a problem if the file owner goes on vacation or time off.
And day by day, it disturbs our work

I feel the same as the other users. In a collaborative work environment, this feature is essential. I'm in the same boat as other users. My UX co-worker is on PTO. So I now have to change the link again for just this one instance to make a small update for the team. When she gets back she will have to change the link.. yet again... this can be cumbersome to the development team if they save or bookmark the link as well as it becomes old or outdated quickly.

So, my coworker will be on PTO and I cannot be able to update the link created by her and already shared with ALL stakeholders. That is definitely a way of how to work on silos, omg

'adding the ability to specify more than one owner for a prototype – and we could then allow all owners to update the prototype link'.

This is really essential and could we have this feature as soon as possible please.

Adobe, do you have any update on this?

It has really gotten old having one "single" person responsible for updating a link for a specific file. Or constantly swapping out links as different people work on the file.

This also affects COMMENTS as well. We have a client who made a bunch of comments on a prototype. A different designer took the file, updated the name to a new version number, and then made the edits. Now if they publish the file, the comments are GONE. If they pass the file back to the original designer, the file is now not the same name, and loses the 'UPDATE LINK' ability. We had to COPY all of the art boards out of the updated file, and paste them back in to the old file. THEN we had to do the same for the prototyping actions... This is just completely backwards. Really upsets me because I sold my whole company on using XD to help my (developer) workflow between designer and developer, and time and time again I have to say 'XD is not able to do this'... Always after the fact too, when something goes wrong.

I would appreciate this. I understand the thinking here, but my coworker is on vacation at Disney World. He owns our design system file and I'm unable to publish updates on his behalf. I had to duplicate his file - which is supposed to be our master reference file - and publish it myself. Now we have two duplicate documents... This won't work for us long-term!

Yes, please, add the ability to specify more than one owner for a prototype. This is the only way to keep the shared links the same, so that a team can work continuously on this prototype. Absolutely necessary for maintaining a design system with XD. Very important for us, too.

This was recently a huge issue for my team. Someone went on vacation and in order for another designer to share for development they had to create new documents. Now the main designer is no longer the owner of the document they need to work from.

This is a major pain point! How can I handle hand-over to an other designer during vacation or when somebody leaves a team? I cannot share my Adobe ID account because designers in the team are working in different companies.

We as the users should have the right to decide who is / are the owner(s) of a document with the according rights.

Even if having multiple owners would be a problem we need at least the possibility to hand over ownership of a document to somebody else.

Especially if the file is used as Pattern Library for other documents! Building Design Systems is team work.

We find this a big hindrance to collaboration and is a significant risk for our design team. If the owner goes on vacation or leaves the company the links in our documents/web pages etc. can no longer be updated/maintained