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)
I’m marking this as feature in the backlog, as this is something we intend to do in the future.
Carlos Sosa commented
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.
Sebastian B commented
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.
Norm Swygert commented
Allowing the original owner to add more owners (and those owners to add owners) would make this a more viable tool for my teams.
Jan Szpakowski commented
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.
Cassiana da Silva Ferraz commented
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
Jessica Loredo commented
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
Chris H commented
'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.
Jason Quiz commented
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.
Ben Berkompas commented
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.
Libby Schlosser commented
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.
Axel Hermes commented
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
What do you all actually do!?!? How has this been sat in 'Under-review' for TWO YEARS?!?!?!
Please get this feature done, I can't believe it's been under review for almost two years.
Me and my colleague need to be able to work on the same files with the same rights so we can share tasks and substitute for each other in times of vacation or illness.
This has put a complete halt to collaboration for our design team. Its a huge risk that a former employee now "owns" the URL that we share prototypes for a client with.
Shall I forward all the emails to Adobe where our client says "stop changing that URL, its getting confusing what version of the site we are meant to be looking at "
back to Zepplin.
I can't believe so much thought needs to be put into this! Just get it done! I guarantee you more people would rather have anybody that has permission to edit also be able to share the file over the way it currently is. This has been a nightmare. What makes it even more of a joke is adobe gives you absolutely no management tools to transfer ownership of an XD file so if an employee leaves and you need to reshare their files after making a change, you have to resave the file to your own cloud account and then reshare and generate new links.
I understand the thinking you're talking about, but I think the implemented solution addresses 1 use case, while causing a major pain point for a lot of other use cases.
The supported use case is:
- I as a user want to create a mock that only I can update, so other users don't change things and update the link without my knowledge.
Here are the use cases where it causes a pain point:
- I'm a UX designer. I make a mock and pass it to a UI designer for styling. The UI designer makes changes, but has to request that I update the mock, even though I trust them to update it when they feel the mock is ready (or after they get the go-ahead from a team leader).
- I'm going on vacation, so I pass some work to another designer to continue while I'm gone. The link to the prototype is in the features or dev specs. They can work on it, but they can't update the shared prototype. I'm on vacation on a beach somewhere drinking mojitos by the gallon and there's no way I'm opening a computer. Now they have to save-as, create their own link, update the link in the features in Jira/wherever, and deal with the developers who saved the original link emailing them asking why the prototype isn't updated.
- I work on a collaborative team where multiple stakeholders work on mockups depending on their area of expertise. For example I do the basic mock and information hierarchy, a colleague deals with animations, another colleague tackles the UX writing, a third designer is in charge of the design system and checks mocks for alignment to product guidelines and adherence to existing components. Every time one of them makes a change, they have to find me and ask me to update the mock, which is super annoying because I've already moved on to something and I'm not their manager, they should be able to update the mock whenever they feel like it.
- As part of our research process we often do field testing in pairs. Each UX will sit with a user in a different place. In the course of testing, my colleague finds an issue with the interaction, or some problem in the mock. They can't fix it/update it themselves, so they have to write it down, find me in between usability sessions, and update it, even though it's something really minor that they could update themselves.
These are all real situations that have happened to me personally. So the implementation I would say addresses maybe 5% of my mocks, where I really want full control. For 95% of the mocks, it's a big pain point.
The ideal solution would be, for each stakeholder in a mock, to allow them update abilities or not.