Allow multiple people to share a link to the same published URL (multiple owners of a Prototype or Design Spec)
Collaborative work: Updating 'share link' of an .xd file not possible on another machine
System: macOS Sierra 10.12.6
XD-Version: 0.8.22.17 Beta
We are working with different people on the same .xd file. Updating the prototype link is only possible on the machine with wich the .xd file was created. The other people can only create new links.
- Create an .xd file
- Publish prototype
- Save the .xd file
- Open the same .xd file on another machine
- Updating the published prototype link not possible (only creation of new link)
Charles Plummer commented
It's been over four years. This needs to happen now. InvisionAPP is looking better and better.
Jeremy C commented
This feature is absolutely essential for those of us working in a team.
Hi XD team where are we with this?
I need to enable my team and myself (as the manager) to allow access to push and update. At the moment it is only the designer that created the file that can update the link. Please this is a highly needed feature.
Was just checking out XD to see if it could replace our current app's Sketch and Invision. The lack of this feature and having a central place to manage client feedback is critical for us so don't think XD will work for us just yet.
This is a must for every business that has a design department of more than one person. Sometimes the person who creates a file or link is not the one to fix or update it. (Such is corporate workflows). If the file has multiple owners I don't see why the other owners can't update that same link, it's ridiculous. Having to change save versions of the file and change the links everywhere is not optimal. I urge you to fix it as soon as possible.
2017: Feature under review
2019: Feature in backlog
2021: Feature under review
2021 (same day): Feature in backlog
What’s the point of asking users for feedback if you never plan on implementing it. Telling us for 4 years now, that you’ll “get to it in the future.” Yeah? When? Cause it’s been 4 years. Maybe by 2030 you’ll have this. By then every team that tried to use XD will be on other software. Like mine, cause were switching to different software providers. Also I teach at 5 Universities as an adjunct and I used to teach them XD. No more, the future UX/UI designers of the world that take my class will be taught other, better softwares.
Additionally, every design event that I go to that Adobe sponsors where you do a software demo, I’ll be the guy making sure to tell everyone there all the shortcomings of this software and why it doesn’t work for teams. And why they should use something else.
“Feature-in-backlog,” translation for those of you who are new. This is where feature request go to die.
please make this feature now. Do not write this subject first in the lists :)
Any updates on this? I believe it's very very necessary to solve this issue. I can't wait on my friend to update a link just because I made a minor adjustment. We really need this feature!
This is a must for a team workflow. How is this not possible after 4 years of requests. Placing the burden of publishing a document update to the same URL needs to be possible for all co-editors. The owner cant be the only person who can publish!
Layne Smith commented
This. Our use case... the primary designers are in the USA, development team is in India. US team builds the designs, India team makes minor adjustments but, since they are not the owners, can't publish fixes without creating and maintaining a separate file that they then share. But then they have to go back and update the original file as well. Oh, and we can have 400 artboards per project so that's a tremendous amount of time wasted just making things match.
This would be huge for me! I manage multiple products with different designers who are often the owner of the source files. I need them to be able to add me as a co-owner on the document so that I can update the links and embed them into our airtable, jira, etc. without relying on the designers to always be available!
We sometimes have 2-3 designers collaborating on one XD project. For some reason the project owner is the only person who can update a review or development link. This can get really difficult when that person is busy with other projects. Is there a way we can make XD allow any user to update the link?
Fadhli Ali commented
Any update for this? It's already 2021
Dávid Hajba commented
Yes, when inviting to collaborate, I want to have the choice to let others update and remove links I created (or will create in the future) and create new ones.
Nándor János Danyi commented
I can only repeat the previous commenters.
This is a burning need for collaboration. Either make it possible to have multiple owners, or just give anyone with an "edit" level access to either update, or create a link for testing.
Dmitry Golovsky commented
With people out for vacations this has been a huge issue for us. Is there any chance that this is being worked on, or any expectations for when it will be worked on? Having to copy files back and forth due to only allowing a single owner has become such a time suck.
Javier Rodríguez commented
To have a backup person in my projects, I need more administrators in the jobs that are uploaded in the cloud to be able to publish them. (update link)
Andy Davies commented
This not being a feature is a huge hinderence to our workflow. If the designer who created the document isn't in the office/on annual leave etc then we can't update a prototype link which is a MASSIVE pain. Could this be added please, we want to primarily use XD for our work but features like this missing are stopping us doing this
This is absolutely critical for our work process. We have several designers working on one project and each should be able to send updates.
I am stunned that this is not already a feature. This is something I just assumed we would be able to do, especially on a collaborative document. Now that our team is in and out for the holidays this is becoming a serious issue for us!
Please consider moving this to the top of the backlog!