SSO is more than just a Workfront configuration.  Workfront is allowed to be accessed as an provisioned app in an environment, users are individually provisioned for each application.  There are specific internal addresses which need to be added into workfront in order for the SSO to be connected to...

I would double check yoru environment because the x button still appears in the right top part of the proofing viewer for me

Do you think that grouping by "entered by" would accomplish a similar goal using the constraints of the system

You're right, it is confusing.

I would start with a task report with some kind of filter so that you get tasks on active projects and not closed projects.  Then, add a column to show who or what role assigned the task in the report.  The act of assigning a task to someone is an event that can be reported on in Workfront to the be...

Have you tried using the checkbox display type?

I think that in this case if you choose to delete the originating request the requester would not be able to track it 

Tacking on to this which is absolutely correct - some of it is change management and training the team on the right process.  If they just look at their previous requests and they see that it's been converted to a request they should know the right thing to do is update the project.

Yeah and if the PDF comments showed up as actual comments in the proof somehow then subsequent reviewers could reply to those comments which would add more value to the process

You are totally right!  My understanding all these years was wrong but to be fair I feel that this is not well explained in the Workfront docs or system admin interface!  To answer the question in the OP I would say it would be a matter of each individual user clearing out their accumulated announce...