no. It's a way for users to push communication from their inbox to Workfront in the form of updates, files, issues and tasks.

Project entry date is what is known as a "native field" -- it came with your Workfront environment and was provided as a way to store the date that the project was created. All customers have this field.   Project submission date is what's known as a "custom field" -- it was created by your system a...

I think Home is the closest you're going to get to Priorities for the time being, but @jerflo will be interested to hear that your users love Priorities.   (I would probably say for the meantime that interested users can bookmark the priorities page on their web browser and use that to access Workfr...

I think I submitted a case once to Support and was told that this is pretty much the way it's intended to function and you can't filter those non-team people out in any way.

there's no single way to view this information without using a third party app -- so as you thought, you need a series of reports.   my "team footprint" reports (I'm sure I'm missing some) include:   * layout templates assigned to team * sharing set up for everything, but primarily: project, templat...

Focusing on your charts question: I don't think you will be able to get all 6 counts into one pie or bar chart. The closest you'll get within workfront is 6 charts on one dashboard (one for each type of menu item). Hopefully it makes sense if I give you the analogy of making a pie chart out of proje...

You absolutely can do this. That's how I ended up deciding that "cine" would work, but yes, ideally if you were building it yourself (I recommend you do!), this is EXACTLY how you would do it -- check and see what the filter would be for one, and then convert to text and add on the others.   Great j...

Thanks for this. By the way, I am making the assumption that your Partner Name field is a text field, so I am answering with that in mind. (You would have had less issue had you made this a dropdown field, but I can't really speak for what's allowable in your workflows.)   Your report filter above, ...

true. I personally have worked in companies that have had thousands of users, so I'm pretty used to seeing 10 Ashleys, and usually just tag in people by first typing in their last name to narrow it down faster (of course, then if you have to tag in a Smith, you're similarly in trouble). So instead o...

If nobody ever has to tag one of these external accounts, I would probably just constrain all the other users to only see users in the primary company (this is a setting on the access levels), and see if that helps alleviate the issue.