<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
0D5KZ00001UgwLi0AJOkta Classic EngineAdministrationAnswered2025-11-05T15:38:09.000Z2025-10-15T07:44:00.000Z2025-11-05T15:38:09.000Z
Can't access the admin console of my organization: you don't have permission to access this page

I can't access the admin console of my organization, could you help me recover my account?

It looks like I am completely blocked.

 

Well, I was trying out the OIDC features of Okta: I was trying to loosen the rules for my fake users to login by disabling the requirement of Okta Verify MFA. My attempt to update the "Default Rule" failed and then I retried a few times. Then my account suddenly stopped working.

 

I was not doing anything bad and I did not attempt to attack the platform. Please help me recover my account if it is possible. Thank you very much.

 

I still have an active session, so I am able to publish this thread. Within this active session, when I click the admin dashboard link, which is https://trial-9026371.okta.com/home/admin-entry, it shows a 403 page:

 

/help/servlet/rtaImage?refid=0EMKZ000000GJmJ 

 

When I try to login in a new browser window, I can't signin either:

ScreenShot_2025-10-15_154441_140


  • Hi @JayC.19450 (Customer)​ , Thank you for reaching out to the Okta Community! 

     

    Admin accounts are subject to mandatory requirement for MFA to access the Okta Admin Console.  The policy changes most likely broke the login flow. 

     

    If you have a paid production/developer account with us, please leverage it to open a case via the support.okta.com site or call the support line (Customer Support Account ID number required) so our Okta Support colleagues can review the matter. If for whatever reason those options are not available for you, please contact your Okta Account Executive or Customer Success Manager, and they will be able to engage the Support team on your behalf.  

     

    If no paid developer or production account is available,  the only option left is to sign up for a new free trial or integrator account with a new email and leverage those for testing. 

    Beyond that, engaging our Okta Sales team to discuss the matter of acquiring Okta Support services would be the only option as it is unfortunately completely outside of the Okta Community Team's scope. 

     

     

      

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

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

    Collect them all. Learn a new skill and earn a new Okta Learning badge.

    Just released: More Okta Community badges just added

    Expand Post
    Selected as Best
  • Hi @JayC.19450 (Customer)​ , Thank you for reaching out to the Okta Community! 

     

    Admin accounts are subject to mandatory requirement for MFA to access the Okta Admin Console.  The policy changes most likely broke the login flow. 

     

    If you have a paid production/developer account with us, please leverage it to open a case via the support.okta.com site or call the support line (Customer Support Account ID number required) so our Okta Support colleagues can review the matter. If for whatever reason those options are not available for you, please contact your Okta Account Executive or Customer Success Manager, and they will be able to engage the Support team on your behalf.  

     

    If no paid developer or production account is available,  the only option left is to sign up for a new free trial or integrator account with a new email and leverage those for testing. 

    Beyond that, engaging our Okta Sales team to discuss the matter of acquiring Okta Support services would be the only option as it is unfortunately completely outside of the Okta Community Team's scope. 

     

     

      

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

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

    Collect them all. Learn a new skill and earn a new Okta Learning badge.

    Just released: More Okta Community badges just added

    Expand Post
    Selected as Best
  • KathyT.73511 (Anthropic Identity)

    The next time you want to test, try creating a test user and a test group. Add your test user to your test group and create a new policy (GSP, Authentication policy, etc) and assign that new test group. That way if it locks out the test user, it's only the test user and not your admin account.

  • KanthyV.53063 (Customer)

    This is a terrible setting. If it is required, then why is it allowed for someone to delete it? Makes no sense. The default rule should be locked in. With big bold wording that MFA is required and the option to delete it grayed out.

  • BrandonB.06003 (Customer)

    Its likely that the policy to access admin required MFA but your user doesn't have the required authenticators in the enrollment policy

This question is closed.
Loading
Can't access the admin console of my organization: you don't have permission to access this page