During the call, we reviewed console and network logs for both the old and new UIs. The old UI uses the endpoint /api/v1/organization/sample, which responds successfully with a status code of 200 OK. In contrast, the new UI attempts to use the endpoint /api/v1/superuser/organizations/sample, which results in a 404 Not Found error. This discrepancy occurs despite the user psathe01 being logged in as a superuser. The issue seems to be related to the API endpoint structure in the new UI, which may require further investigation to determine why the endpoints differ and why the superuser role doesn't resolve the issue.