Auto Provisioning for only new users

[#1]

When using the auto provisioning process, data for attribute fields are passed for new user accounts and existing user accounts. Our goal is to create a process for auto-registration. If a person does not have an account and attempts to access Workfront, a basic "request access level" user is created. However, the "home group" field is required. I would like to have the "home group" field only updated for new users. Since we attempted to use a default value for the home group for new users, applying it to existing users can break reports and structures throughout the system. This functionality is preventing us from using the auto provisioning process.

[#2]

I hope I am looking for the same thing. I would like to select the default Home Group in Auto Provisioning. Currently, the Home Group is required field and no way to decide what is assigned without creating a mapping to the source. This seems obvious to allow a default for a required field.

[#3]

I would love to do seomthing very similar when new users try and come in then use SSO to initially setup a user (with a specified layout template, group, company, access level) - ideally would like to use mapped attributes to set them up but not re-write every time the user comes in (so they can put preffered first / last name in if they want)

[#4]

Upvoted! I agree that there's currently a bit of a gap in Workfront when it comes to the auto-provisioning process. For this reason we have decided not to map any attributes from our company's user directory to Workfront with the exception of firstName, lastName, and emailAddr, basically the bare minimum. We are utilizing a custom-built Fusion scenario to make sure our newly auto-provisioned users are placed into the correct Company and Home Group; however, it would be great if this was something that could be configured in the system without resorting to automation tools.

[#5]

I agree with Andrew Parsons. We use SSO but can only map name and federated ID. I would like to be able to set defaults for all other options, this includes if we have additional/custom data fields. We've created the list for the additional data, but of course just like the WF data, we can't default most fields to what we'd like them to be. This I find a major issue with an application that is accepting data entry. How can a field not be setup with a default?