Anthony,When I tried that it gave me an error : method PUT is not allowed for authorization type COOKIE

Thanks for the reply. To clarify, the goal was to create an API key without turning off SSO for the entire instance, not to automate the creation of API keys.

The documentation says that to generate an API key for a non-admin users you have to disable SSO for the entire instance. Is there any other way to do this? Maybe through Fusion?

One of our departments asked for a list of all contacts associated with a project. The list would include current WF users from our company and non-WF users from other companies. The format would be similar to the "People" tab expect it would include a row for each external contact. Additionally, th...

Please take steps to make Edge Chromium an officially supported browser for Workfront.

I have looked over this documentation, but I'm unable to prevent specific users from showing up in the task assignment suggestion. The users in question are planners and the tasks have a job role assigned. The problem is that the planner's name always shows up as the first suggestion. https://one.wo...

I created a parameter report with name and forms columns. I set the the report to run as me, an administrator, so that all users would see the same data when they visit the report page in Workfront. The name column populates correctly, but the forms column only shows custom forms that the user alrea...

Thanks for the advice. We have a demo instance (not our sandbox) that is separate from our main instance. I don't know the exact order, but I ended up deleting the user from both instances. Then I recreated the user in only the main instance.

I am trying to change the access level for one of our users and I get the following error: "This user has already been provisioned for proofing on another Workfront account". I believe this is due to a demo instance of Workfront that we still have running. What is the proper way to resolve this?

Thank you both for the responses. I was hesitant to use "Has Resolvables" because of the ambiguity. The Fusion FLO I built does a search for Issues with a ResolveProjectID that matches the current ProjectId. If it finds a match, I know that project was converted from an issue. Jason Saunders