Skip to main content
Level 4
Oct 26, 2026 5:02 PM UTC
New

De-couple Auto Provisioned users Home Group from Home Group of System Administrator

We’ve been working with Workfront Support on this issue, and I wanted to see if anyone else is struggling with this.  Here is how support described the issue:

“Currently, when a user is auto-provisioned through SSO or the Adobe Admin Console, Workfront assigns the new user's Home Group based on the Home Group of the administrator who triggered the user creation process, which is often the primary system administrator.”

What this means for us is that our administrator is in a Home Group that best fits the permissions of our lowest-level users.  There are many downstream effects of this.  Recently, we wanted to enable the ‘Announcement was added’ notification for our admins, but NOT for our lowest-level users.  Unfortunately, this isn’t possible in the current configuration, because if we enable it for the ‘All requestors’ Home Group, then all of our lowest-level users will also be notified. Because our admins weren’t getting these notifications, we missed that Adobe changed the rollout date of several recent Workfront updates. 

I wish Workfront would decouple auto-provisioned user’s Home Group from the System Admin Home Group; the current setup doesn’t make any practical sense.  

4 replies

HeatherRo13
Adobe Champion
Adobe Champion
Oct 28, 2026 2:21 PM UTC

Hi! Its typically best practice to have Admins in their own separate Admin Home Group specifically because their settings will need to be different than others.
We have a process where I get auto notified when an new user is added through SSO and that is added to an action queue for me. My next step is to go into that user’s settings to update them to the correct Access Level, Layout Template, Role, Group and Team based.
Yes, its an extra manual step for me, but its a pretty easy process that works well for now. 
Also make sure the systems notification action is unlocked at the group level so it can be customized per group.

 

Translate
user01245Author
Level 4
Oct 28, 2026 3:23 PM UTC

Thank you for the reply!

So when users are added automatically, are they added to the same Home Group as your main admin? I’d love to have my admin account in the ‘Admin Home Group’, but if I do that, then all my auto-provisioned users are put into that group when their accounts are created. I can go in and update their accounts as they come in, but I really don’t want those users ever becoming part of the Admin Home Group.

 

Hopefully i’m making sense, haven’t had any coffee yet today 😅

Translate
Russ_Nelson
Level 2
Oct 28, 2026 5:29 PM UTC

This has come up for years (older thread). Until it’s fixed, here are three ways people work around it:

  1. Map Home Group at sign-in. On orgs onboarded to the Admin Console, go to Setup > System > Single Sign-On (SSO) > Adobe tab > Add Mapping. You can set a Workfront field from an IdP attribute or a constant, with conditional rules. Put any “Always” rule last, because rules below it are ignored. If your IdP can send a department or role attribute, you can route requestors to one group and admins to another. The catch is that mappings apply at every SSO sign-in, so they overwrite manual changes. Only map the field if the IdP is your source of truth, and test in a Preview or CR sandbox with an admin and a non-admin account, as the doc recommends.
  2. Correct it after creation with Fusion. A scheduled scenario finds newly created users (for example, by access level or by sitting in the default group) and updates their Home Group. Several admins in the older thread solved it this way.
  3. Holding group plus a report. Send new users to a dedicated “new users” group and review a daily report of its members. It’s manual, but it’s predictable.  This is the suggestion from HeatherRo13

If Support is right that new users inherit the Home Group of the admin who triggered the creation, also check which admin account that is. Moving that one account into a dedicated intake group may be the smallest fix. Once your admins sit in their own Home Group, you can turn on the announcement notification for them alone.

Translate
Russ Nelson, Founder, Prolifico Digital
user01245Author
Level 4
Oct 28, 2026 6:18 PM UTC

Thanks Russ!  I’m going to see if any of those options will work.

You reminded me that this change was also triggered by the move to Admin Console. As mentioned in the thread you linked, the behavior used to be that whichever Home Group was first alphabetically was the one assigned to new users.  This was easy to work around, as we just setup a group called ‘*All Requestors’.  

 

Like almost everything related to the Admin Console rollout, the behavior change that came with it was a regression and worse for our users and admins.  It’s unfortunate that this is an issue folks have been working around for 8 years.

Translate