Comments
-
Hi@"Jay" Thank you for your response. That would work and get me most of the way, I’ll just create a link per client, manage accordingly in comms and just segment then upon submissions (if needed) as opposed to automating before hand. This will work too for another automated web and database backup I’m looking to do with…
-
Structure I use for design projects that scales well: root folder: * 2024 * 2025 * etc… next folders: * Operations * clients * sales * accounts * admin (this helps keep sort order without being alphabetical) In clients folder * client A * client B * client X within each client Folder there (and works for all other folders)…
-
This is something I've been wondering about too. Only (annoyingly) manual way I've been able to (kinda) do this is to have a 'baseline folder' (essentially just my file templates and folders pre-editing), then just clone this structure. Not a solution but more of a work-around that gets some of the way there. I'd be…
-
Thanks! Can confirm it is VERY scalable - even across years!
-
I've been an admin on my team account for a few years now and it's been working great. When bringing people onto the team and syncing design files, a usability tip we've found works well to get them started is reverse dating for version control. Rather than 'filename.indd', 'filename-new.indd' 'filename-new-2.indd'…
