When I see this, it's usually because the individual is signed into a different Adobe ID than the one associated with Workfront. In that case, they should log out of Adobe and sign back in with the credentials for your Workfront instance. I hope that works for you!

Unfortunately I think this is going to be a fairly manual switch. Here's what I would do (as an admin who doesn't have Fusion because I suspect Fusion might be able to make this easier for you): Add both job roles to the user. The weight of these job roles might be 100/0 until after the new role tak...

I tested this in my Preview environment and you're right: I can't get custom statuses for a specific group to show up as an option for Team settings. I would doubly confirm this with support and, if they say this is as designed, submit an idea. I'd upvote an idea to allow custom statuses to be used ...

By design, a project report won't be able to pull in much task data. A column in a project report can pull in a collection of tasks and you can lightly format that collection, but that's about it. If you build a task report, though, you can get closer to what you're looking for. I would group your t...

It's been a while since I messed around with statuses, but what I do remember is that I made a bit of a mess of it at first. Support helped clear up what I did and how to do it better. I say that up front because that might be your next step. If you haven't already, study this article. For statuses ...

We also have SSO and add external users manually. The process is different depending on whether you've been migrated to the Admin Console or not. I would start here. Note that all users need to have a free Adobe account. These non-SSO users then will be able to log into your instance with a username...

I see: it's about statuses. I've heard others recommend keeping statuses relatively simple because, as you've discovered, managing them is sometimes not easy. Defining clear governance around statuses can help reduce how often someone asks for a new status. For example, in our organization we use: N...

I might not entirely follow what you're suggesting, but I've thought a lot about our own group structure, so I'll share what we've done. We use the Companies field and Groups. Here's how it works: Companies: The vast majority of users fall under our actual company name. I create a new company when w...

This add-on is important for adoption. My project managers try to keep all communications and requests in Workfront, however it's a battle. Additionally, when trying to implement new groups into my instance, this add-on is often a critical bridge to adoption. We have a couple dozen users who use it ...

@douglasca Keep in mind that my idea above is simpler than what you're asking for: When there is an approval on an issue, I want the issue to document that decision forever, even if the issue is converted to something else. But I'll play ball with your scenario the best I can. I can't say I've heard...