Grouping by client:
How would you use it?
I was really just thinking that you’d use it the same way we use the Projects groupings. My company can have multiple projects for a single client OR a single designer could work on a single project but be half time with two clients.
What this bucket should add/remove from projects in this bucket?
As I started to think about how complicated this can get, I think that I actually need more ways to re-organize our flows. A “Project” could be a client or a “Project” could be any of a number of project teams with a single client, so at a consultancy this can get messy. And, navigating my numerous flows can be cumbersome.
For example: I have my current client organized by platform (Web, Android, iOS), but I could have organized it Product Team (there are 5). Finding a mobile flow in that drop down is really cumbersome because there are so many. And, I’ve learned I shouldn’t have organized by platform, because there isn’t enough difference between mobile platforms. But, I can’t reorganize how my Flowmapps are bucketed or move flows between projects to fix the issue.
What restrictions should be added when a project goes into this bucket? And most importantly, why do you need a password and from who?
My client is high security. All of our visual designs are password protected, because we have a non-disclosure agreement with them. So, since our flows include screens that are usually password protected, we were very worried they would take issue with us using the Flowmapp tool.
We just need to password protect them from anyone that isn’t working on the project.
Transferring a project
What about usual Project transfer between users?
You will not lose your account after this.
That should work. I hadn’t seen that info before.
Is it possible you can share the XML file with me( via direct message if you want) so we can check it with engineers and see if it possible to implement?
Unfortunately I am under a NDA with our client. i don’t think I can share any files, but it was created in draw.io and exported as a pdf. so you should be able to create one that way for testing implementation.