You’re seeing two different things:

• In the browser you can open your ODC personal environment / ODC Portal.
• In ODC Studio you get the “Access to this organization is restricted – You don’t have permission to access this organization” page (like in your screenshot).

That mismatch almost always means the account that Studio is using is not the same account (or not the same tenant/organization) that has access in the browser.

Try these steps in order:

1. Confirm the Organization URL in Studio

In the ODC Studio login screen, the Organization field must match exactly the domain of your ODC tenant, in the format:

• yourprefix-dev.outsystems.app (Studio)
• But this must correspond to the Portal domain yourprefix.outsystems.dev Error logging into ODC Studio Client not found

So:

1. Open your ODC Portal in the browser.
2. Copy the domain prefix (the part before .outsystems.dev).
3. In ODC Studio, set the Organization to:
   thatprefix-dev.outsystems.app.

If these don’t match, Studio will try to authenticate against an organization where your current user may not have permissions, and you’ll get the “access restricted” page.

2. Make sure the same OutSystems account is used

The browser might be logged in with Account A, while the Studio flow ends up using Account B (for example, due to another session or a different Microsoft/Google login).

When Studio opens the browser for login:

1. On the “Access to this organization is restricted” page, click “Log in with another account”.
2. Explicitly log out of all OutSystems accounts in the browser.
3. Log back in using the exact same account that you use to access the ODC Portal successfully.

If you are part of multiple organizations/tenants:

• Confirm in the Portal that the account you are using actually has access to the personal environment for that organization.
• If you recently spawned a new personal ODC environment, make sure you are using the new tenant URL and not an old one that may have been decommissioned. Both Personal Environment/Service Center are unavailable

3. Check for local issues on the login flow

The ODC Studio login works like this: Logging into the ODC environment

• Studio → https://id.outsystems.dev → https://os-pre-unified-login.outsystems.app → http://127.0.0.1:<port>

If something locally blocks the callback to 127.0.0.1:<port>, Studio may fail to complete login correctly and show odd behavior.

You can try:

1. Disable firewall/antivirus momentarily and test login again.
2. Try a different default browser (some extensions like ad blockers have caused login errors) Both Personal Environment/Service Center are unavailable.
3. If you’re on Windows 11 and recently installed updates, check whether Windows Sandbox is enabled or if you’re affected by the known issue:
   • Disable Windows Sandbox.
   • As per OutSystems support, some users solved login problems by uninstalling specific KBs:

     wusa /uninstall /kb:5066835
     (restart)
     wusa /uninstall /kb:5065789
     (restart)
     

   Only do this if your IT/security policies allow it, and ideally with IT support involved. Logging into the ODC environment

4. If none of the above works

Since you can access the Portal but not via Studio:

• Confirm in the ODC Portal that your user is listed with the correct role for that organization.
• If you’re using an ODC training or partner tenant, ask the tenant admin to verify your access.
• If everything looks correct on the Portal and the issue persists after trying the steps above, open a ticket with OutSystems Support from your account, describing:
  • The exact Organization value you use in Studio.
  • That you can access the Portal but see the “Access to this organization is restricted” page during Studio login.
  • Any firewall/AV/browser details you’ve tried.

If you share what Organization value you’re entering and whether your OutSystems account belongs to multiple orgs, I can help narrow it down further.