This message was deleted.

I understand this is urgent. Based on similar cases in the GoodData community, here's what likely happened and what you should do: Likely Causes 1. Broken identity/auth mapping – When user provisioning changes are made, the `authId`/OIDC identity mapping can become broken or mismatched, leading to loss of access even for admin users. [Missing authId fix] 2. Lost admin group membership – Changes to user provisioning or authentication configuration (e.g., OIDC/Auth0 settings) can inadvertently remove a user from the

adminGroup

. [Admin group fix] 3. JIT provisioning misconfiguration – If you adjusted JIT provisioning settings, this can cause authentication failures. [JIT provisioning] Immediate Steps to Take 1. Capture a

traceId

– Open your browser's Dev Tools → Network tab, reproduce the error, and copy the

traceId

from the failing request's response. This is critical for support to investigate. [TraceId usage] 2. Check if another admin exists – If a colleague has admin access, ask them to verify your user exists in the correct org, that you are in the

adminGroup

, and that your `authId`/OIDC ID is valid. [Admin/authId checks] 3. Contact GoodData Support directly – Provide: ◦ Your GoodData hostname (e.g.,

yourorg.cloud.gooddata.com

) ◦ Your email address ◦ The

traceId

from step 1 ◦ A description of the provisioning changes you made before losing access Since there is no self-service way to repair a missing or incorrect

authId

, this type of issue typically requires GoodData Support to fix on the backend. [AuthId repair] > Note: As an AI assistant, I cannot directly access or modify your account. Please reach out to GoodData Support as soon as possible for hands-on resolution. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups. 👀 Our Support team monitors all messages and will jump in if needed.