The scenario is this
How do I stop that notification from going out to the requester?
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
In the user's notification settings under the Requests I Have Made section there is an option for A document is changed or uploaded on an issue for which I am the primary contact. I would think that this is the setting that is sending that notification to the requestor. If you uncheck that on their user account they should not get that notification. But I always like to confirm that there is no reason that they would need that notification for any of their other Workfront work because they wouldn't receive any of those notifications if you uncheck it. Also those settings are editable by the user so if they are savvy and think "why aren't I getting that notification anymore", they can look at their settings and turn that back on and you wouldn't know it.
Hope this helps
Views
Replies
Total Likes
This is what I thought, it's all or nothing. Wondering if anybody else has found a workaround for this, or experiences something like it and how they deal with it.
Views
Replies
Total Likes
In my past Workfront life we converted all issues into projects and did not give the requestors access to the projects. We then did all of our proof routing in the project so they were never alerted when a document was added. When ready to share with them we simply added them to a proof workflow.
Views
Replies
Total Likes
We do the same as Tracy; requests are converted to projects and the requester gets no access to said project except when explicitly given by the planner on an object-by-object basis.
Views
Replies
Total Likes
Ah yes - the video team can't deal with projects but it's a good point and I will tell them that's an option, maybe it will sway them to move to that process.
Views
Replies
Total Likes
Views
Likes
Replies