Start an Access Request tile issue

[GauravJain]

Hi

User 'A' part of sav role "ROLE_SAV_ENDUSER" tries to raise an access request after clicking on "Start an Access Request" tile present on home page.

As the Sav role doesn't give access to raise request for others, still when user selects "Someone Else", Saviynt disables "Application" option but "Role" option is enabled and user can click on "Role". On next screen, user wont be able to select any other user and he can raise role request only for self. 

this is a conflicting behaviour as the user must not be allowed to select "Someone Else" when his/her sav role doesn't grant him required privileges?

is it a bug? OR by design its like that only which is definitely not user friendly.

Regards

Gaurav

[naveenss]

Hi @GauravJain  you are seeing this "someone else" since the ROLE_SAV_ENDUSER role has "Request Enterprise Roles- Classic Experience" feature access. If you don't need this, create a replica of the same SAV role and remove the above feature access. After this, you will only see the option to request for self. 

Hope this helps. Let me know if you have any questions. 

[GauravJain]

Thanks @naveenss . Yes, i can always create a custom sav role to overcome this but i wanted to understand why it was designed like that.

is it because Saviynt do not have a separate navigation item for "Request New Enterprise Role For Others" ? and both the options Self / Someone Else is combined in one navigation item "Request New Enterprise Role".

[naveenss · Accepted solution]

Hi @GauravJain looking at the design, I believe that is the case. Saviynt do not have a separate option to request enterprise roles for others. There is only one entry point for both self and others. Hence, the option displaying "Someone else" in the new experience explains the case. 

I hope this helps!

[GauravJain]

thanks for the confirmation.

[rushikeshvartak]

You need to request as new feature to hide someone else based on query.

[GauravJain]

Hi @rushikeshvartak can you please elaborate more on this? 

[rushikeshvartak]

Since its not supported and expected behavior as per product design . You need to raise enhancement ticket to hide someone option as it will need code change