You could create a report/dashboard that reports back tasks assigned to a person based on direct assignments AND tasks assigned via a Team. Our problem is we assign via some teams because anyone at any moment could work on it. So we assign to the Proofreadong team, but who grabs it now, or later, co...

Thanks Anthony for confirming my suspicions on how it would work. I guess when we cross that bridge (to offer/train for versioning) we'll have to see if the tools of versioning trump the annoyance of so many routings to manage.

I'm curious about this too, but for a different reason: If a routing is sent with 15 pieces of artwork (concatenated by WF Proof; i.e., the user put 15 PDFs in and had PHQ combine them), how would versioning work if we wanted to: Version all 15 again (does PHQ have any idea how to match them up agai...

I'm hoping to see a clever answer as well…because as of now, my answer would be "make them use a dashboard." (We used layout templates to force the first thing a user sees to whatever most important list we want them to. In the case of Workers, it's an assigned tasks list with highlights for overd...

I prefer to think of these as "hacks"‚Ķ  ...and this is a minor one in the grand scheme of Workfront hacks. More like a benign "trick." I've seen some of atApp's tricks (these are "hacks"...LOL), and shortly after launch I had to put together some doozies (I barely can handle text mode and you wan...

One issue will how to explain show/hide logic and menu choices in such a format. If you're interested in samples of ones I've created for our team, contact me directly (I can't post them to a public forum).

Doug, tricks like these are among the plethora of things I need to memorize when trying to solve reporting problems. Any tips for getting them to stick in my brain? 

I ran into this a week or two ago. Took me a fair bit of time to figure it out. Very confusing. I've long since told users the only reliable info is in WF Proof itself, or the proof status dashboard we created. Ignore the Update stream, force reviewers to use WF Proof for all comments, etc.

This is probably a messy long-way-around, but: If this person works on confidential projects quite a bit, what if you created a separate user login for her and her own "pocket universe" to work in via controlling everyone's access to items created under that login, similar to how others have separat...

That was always my suspicion (ratio or "percentage of unused space") but just not enough To Do bandwidth to test. It's a "nice to have" when I have lot of "must have now" testing to do. 