How does the report work? Does it pull in all of the creative brief changes for a single project or multiple projects? If multiple, is it grouped by project?
We have a similar situation in that we have a lot of projects - we need a brief - what is the best way to have a brief apply to a bunch of different projects - how do we best manage that process, but also how do we manage updates to the brief -> pushing updates to the resulting projects. Currently ...
I'm not sure if this helps but.. If I do a force logout from Workfront and close the tab -> I go to Okta and click the Workfront button -> A new tab opens for Workfront and (very briefly) I see a message on my screen "Signing in to Workfront" - I never see username or password fields.
In your example, when you open the workfront url does it have /login at the end? If a user was directed to this instead of the root domain URL they would be bypassing the SSO by logging in to the system directly.
I have nothing to add to the conversation but I am curious if you're willing to share more information about your workflow. Specifically I wonder why this task is specifically relegated to mobile devices, it seems like no one has computers? From a practical perspective, viewing, and commenting on ...
In my instance each request is actually a container project, when a request comes in it is an issue within that container project. That container project has it's own share config just like anything else. There is a slightly different configuration when you have a project set up as a request queue...
If this is something you wanted to do I would think generating a proof would not be the most efficient route. If you want someone to press a button and approve everything this sort of goes against the granular and individual nature of Proofs where commenters can go virtually pixel-by-pixel and ask ...