<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
0D5KZ00001I88kd0ABOkta Identity EngineIdentity GovernanceAnswered2026-01-26T09:00:30.000Z2025-08-21T22:45:42.000Z2025-08-22T17:06:28.000Z

abcn0 (abcn0) asked a question.

access request request type x acess request conditions

I HAVE A QUESTION. I SEE THAT VIA REQUEST TYPE I CAN SEPARATE DIFFERENT PROFILES FOR DIFFERENT TIMES TO APPROVE THEM. OF COURSE, BY CONNECTING BUNDLES, THIS WORKS EVEN BETTER, BUT I CAN USE OKTA GROUPS AND BUNDLES.

 

However, without conditions, I can't set the same requester group (e.g., everyone >) to request different profiles, and each profile to be a different planner schedule or planner group for each profile selected from the OKTA groups for the request. If I create separate conditions via priorities, I understand that the others don't appear, or do they appear?

 

My other question and response is whether the request type will be discontinued over time, and should I immediately migrate my flows and use only the conditions?


  • Hello @abcn0 (abcn0)​ Thank you for posting on our Community page!T

     

    The Okta Community Questions forum isn't really meant for in-depth troubleshooting.

    If you already have a Support ticket open, then I recommend continuing the discussion with the assigned Technical Support Engineers. They'll be able to access additional tools and resources to help you get to the bottom of it.

     

    hank you for reaching out to our Community and have a great day!

    --

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

    Just released: More Okta Community badges just added.

    Expand Post

Loading
access request request type x acess request conditions