https://next.frame.io/ website I see 5 available accounts which i can fully access.
https://api.frame.io/v4/accounts API endpoint only returns one account (payment primary account)
I need to access the other accounts via the API, Please help 
It seems the issue is related to the initial adobe SSO sign-in modal where you select an account, that account then sticks and doesnât allow inter-account communication.
* Update, If you sign in with personal profile it shows all accounts, but if you select any other account will just show that 1 account in the API response.
Adobe, please fix this issue.
hi @james_phoria this is by design as this is a part of Adobe IMS (identity management system) where the profile you select is what receives the âentitlementsâ that allow you sign in to use what you have access to. So if you are a part of an enterprise company at XYZ and you log in and select XYZ profile, you only have access to entitlements for that one profile.
As you said, selecting a different profile (such as personal or one that does not have a specific adobe managed frame account) is the way to see all of the other accounts via the API as there is no specific entitlements to Frame.io that is specific to that profile.
If you wanted to switch profiles you will have to go to adobe.com and log out in order to get the prompt to select when logging in (otherwise cookies will just auto-log you in to the last known profile).
Alternatively, if your company allows it, you can go to Adobe.com, click your profile, click manage account and then find the setting that defaults to logging you in automatically to that selected profile (I forget where this is, as I donât have this option within Adobe, I have to sign out completely to switch profiles)
Hi Charlie,
Thanks for your reply 
and confirming that this is a design decision not a bug.
For a general users this process isnât common knowledge though and once its stuck in their browser its unlikely they will think to go to adobe.com to sign out, especially if I am trying to make the process as smooth as possible.
To add some more complexity, the application I am building this is VR based so browsing to adobe is even more painful 
One idea that could solve this is if there was a way to provide an override profile selection url param in the SSO flow that auto selects âPersonal Profileâ e.g â..&profile=personalâ
Im just trying to make the sign in flow as simple as possible for non technical users and eliminate any risk of wrong profile selection.
Account switching is a very important core feature of the app I am building, it will have some big enterprise users using it
The best way to force users to re-select a profile would be to clear cookies on your side on logout, as that should remove any known sessions and the user can start clean.
One thing that I would recommend adding for authentication to make it super simple is the concept of an authentication code (similar to what we do for C2C) from a web browser to device. This means youâll have to host a server somewhere to handle this code exchange but if you want simplicity, having someone log into frame on a browser and then connect to the headset via 4-6 digit code would be the best way IMO. This way the device doesnât have to host/compile the oauth libraries needed, you just have to send the access code to make the calls on device.
LMK if you run into any issues and would love a demo when you get to that point! I have a meta quest 3 so happy to test and provide feedback if youâd like!
Thanks Charlie
Good idea, Ive seen this flow used before and it was much easier than typing in my password in headset, especially without controllers.
Iâll likely explore this soon. Clearing the cache on a separate device, triggered triggered from a headset based flow may be tricky, but Iâve got some other methods also on the go so will see 
Iâll get this SSO profile flow figured out, then I should be able to share a demo! 