<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D5KZ00001WYNmE0AXOkta Classic EngineIdentity GovernanceAnswered2026-05-23T09:00:27.000Z2025-10-27T14:14:30.000Z2025-10-31T15:03:51.000Z

py2cd (py2cd) asked a question.

Removing Service Accounts from Access Requests Request on Behalf of

We are looking to roll out Access Requests and have turned on the "request on behalf of" feature. When we look at users in the request on behalf of option, we see service accounts listed. Is there any way to remove them and make them not show up in the request on behalf of drop down? If so, how do we accomplish this?


  • TimL.58332 (Workflows)

    @py2cd (py2cd)​  -- The exclusion is based on the "audience/scope" of users that are allowed to interact with the request. If you have it set to "Everyone" than since Service Accounts are also just users they would be viable targets. However, if you had it set to Group only the users contained within the Groups would be viable targets.

     

    Here is an example: First user is not in the "Group" the second user is in the "Group"

     

    image image

    Expand Post
    Selected as Best
  • User17157611498146715886 (Customer Support Online Community and Social Care)

    Hello @py2cd (py2cd)​ , thank you for contacting Okta Community.

     

    Try adding a condition that would prevent service accounts from having access to the Access Requests. Using the Okta Expression Language, you could filter them out using an attribute, like user.type. The following articles would have more details on this:

    Access request conditions

    Create an access request condition

    Okta Expression Language overview

     

    If your service accounts are the same type as your regular users, you may want to look into adding a new user type. This can help differentiate them from regular users. Here is the guide:

    Create a custom user type

     

    Regards. 

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Expand Post
  • TimL.58332 (Workflows)

    @py2cd (py2cd)​  -- The exclusion is based on the "audience/scope" of users that are allowed to interact with the request. If you have it set to "Everyone" than since Service Accounts are also just users they would be viable targets. However, if you had it set to Group only the users contained within the Groups would be viable targets.

     

    Here is an example: First user is not in the "Group" the second user is in the "Group"

     

    image image

    Expand Post
    Selected as Best

Loading
Removing Service Accounts from Access Requests Request on Behalf of