When creating new accounts, make custom roles available to assign

[SaraJL]

Hello everyone!

I have custom roles created in ArcGIS Online - but these roles aren't available options when setting up new accounts. It would be nice of all roles created in the organization could be available!

This is what shows up:

I created an Analyst custom roles that gives specific permissions to my users (ie like creating groups with shared editing capabilities, prevent people adding other users outside our org for FERPA reasons, etc) but I can never get the custom roles to show up as available options:

So if I add a bunch of new accounts, I have to keep going back after the accounts are activated and updating the role to the correct role. 

It would save some time if custom roles were an option! Unless there is a setting I'm staring at that I'm missing. 

Thank you!

[PatIampietro]

+1.

I believe this is because Custom Roles that include Admin privileges can not be assigned as User Defaults or on account creation, which has been requested in existing ideas. <Will add links when I find them>.

[SaraJL]

@PatIampietro Really the only difference between the custom role that I created (Analyst) and the Publisher role is that I blocked users from being able to add people from outside our org and I also granted users the ability to create ArcGIS Groups with shared editing abilities.

I was running into a lot of issues where users would try to create a group and then they would email me saying ArcGIS was broken because they were unable to edit projects. So I gave everyone the ability to create shared groups (because I don't care if people create shared editing groups or not). I suspect that it might be this setting that is considered an admin setting?

I could understand excluding Administrative roles to some degree, but it would be nice to have a setting of some sort to be able to choose which roles to include, versus just excluding any roles if it has 1 of the admin permissions.

[PatIampietro]

@SaraJL Create shared update groups is considered an Admin level privilege (although whether it should be or not is debatable).