Team projects / team cloud storage
I want it so that the cloud space would work as a team space, not only the individual users.
team cloud space
Matt Adams commented
Yes, I agree, with every document created we need the entire team to see it. It would be great if the users on the team account could browse all projects regardless of who created it and without the need to be invited.
Adam Trabold commented
This would be incredible. We currently use GDrive (in the past Dropbox) to have shared cloud access to files. It would be great to have organizable shared spaces for projects that I could invite people to.
Would be even better if this could be duplicated for share links -- i.e. "x people have access to the y file space" and "x people have access to the z share links in y file space."
I have been thinking about this feature a lot lately as my team and I come up with a way to collectively manage our designs/prototypes for multiple very large and complicated enterprise systems. Some of the challenges we are having could be due to our global team presence, but I'm inclined to believe this is more common and not a unique problem:
As I see it we need:
1. a way to share multiple XD files across multiple designers who all have first-class permissions to the file - eg. it's not shared by one designer with others - but collectively owned by the team. We currently have around 27 different initiatives with between 1 and 10 XD designs each representing a different feature, application and/or versions which vary in size but average appears to be around 12MB - needly to say there is a lot of content (almost 4GB of XD files alone) and it's growing every day.
As part of this the open dialog in XD isn't very robust when working with cloud documents. specifically in that users first have to know if they were the original creator of the file or it was shared with them (so they can look for the file in the right place). second, cloud folders are not shown in the open dialog being there isn't really any organization and open simply presents a giant list of prototypes
2. We need a way for any designer on the team to publish to the same prototype URL - we publish primarily to collaborate with the business and technology stakeholders and since any designer could make a change to the file, any designer should be able to update the prototype without needing to re-share with all of the different stakeholders (e.g. use the same URL) typically our stakeholder group on any given release is around 10-15 people but as our system continues to evolve more and more people get involved and we'd like everyone to be on the same page.
3. Versioning - There are some interesting new features for versioning - but it seems this is versioning of the file not versioning of the prototypes *admittedly I need to play with this and test more. - the approach seems so far - but the ability to remove (unmark) a version seems too easy and could be accidentally done We will need and want to keep a version history for minimum 3 years (minimum 6 versions and likely more) without risk.
It might be useful to publish the marked version name with the prototype - today it seems the only way Identify which version of a prototype is being viewed is to change the title at the time of publishing the link.
It also seems that the version dialog and the published links have no bearing on each other.
Published prototype link management should be organizable ... what would really be nice it to be able to share a catalog of all published prototypes (and versions) and invited folks could browse the catalog of prototypes. - effectively the manage links page made available to anyone ** with some organization ability (folders)
4. At first I though the ability to select the type of view setting was kind of neat - but now I'm feeling it's more of a nuance... custom seems to be the solution but custom view setting doesn't allow showing dev spec. instead of the view setting templates I'm now of the opinion that the older approach made more sense - just allow the publisher to select all of the features that want to allow, on/off, with 1 publish (including dev spec)
We have mostly been using CC files to sync our collection of file across the team (a la dropbox style) - this is not the most efficient approach. Effectively each designer has a complete copy of a the entire body of work and eventually the team's body of work will out grow the physical storage on their machine. Additionally the whole process is manual and ripe of human introduced error.
Just adding some thoughts while they are fresh in my head.
Adobe has done some good updates for multi-user collaboration - but it's still based on the concept that it's an individual sharing with others - it's supposed to be creative cloud for TEAMS and we need capabilities for all assets and libraries to be available from a group without the need to invite each member. perhaps a group capability? Though right now I would almost prefer this be more automatic for groups.