Default Role Issues

[Former Member]

Hello experts, I have a few questions around default roles

I have configured the role default parameters in SPRO and I have also set my default roles within NWBC. I’ve found that once configured the
default roles can be seen when looking up a users existing access. The thing is if I don’t select that role from existing access it won’t provision. Is
there a way like in 5.3 that it will just assign based on selected attributes?

Also, I want to be able to submit a request with just the default, but during a request I get an error that you must select at least one role. Is there a way to get around this when combined with above?

Thanks!

[Former Member · Accepted solution]

Hi Kyle,

Did you manage to resolve this after?

I have been playing about with the settings also and it seems it can be slightly "hit and miss".

I set the parameter 2011 to "Request" and made it consider the "Company" in the request as the determining attribute. I also enabled it for the request type 001 (new user), so default role X is only considered when creating new user accounts for Company X etc, with default role Y considered for new users in Company Y (this is done on the NWBC side).

I don't think it is possible to send a blank request in hope for the default roles to be only assigned. Upon submission, the ARM tool will look at the request being submitted and tell you to put in items. The solution may be to assign a "System" (rather than a role), but this could well require tweaking/redesigning both your initiator and workflow to cater for "System-only" access requests.

Hope the reply/answer helps.

all the best