VCF Automation 9.0.0 & 9.0.1
There are some known issues around logging directly into VCF Automation Organization/Tenants which can cause these unusual scenarios.
The current supported method of accessing the Organisation through "Launch organization portal" is the correct way to access any Organisation for the moment
The issue is tentatively planned to be addressed in the VCF 9.1 release.
This is outlined in the following KB:
Using a tenant-specific URL to open a VM-Apps-Tenant in VCF-Automation fails
Please first log into the Provider Portal rather than directly accessing the Tenant URL
The fix for this issue is tentatively planned for the VCF 9.1 release as per the Knowledge Base article:
Using a tenant-specific URL to open a VM-Apps-Tenant in VCF-Automation fails