About the specifications of multi-headed owners when authenticating aibo-linked application

>Dear aibo developer support representative,

I have a question about the OAuth authentication flow of the collaboration application when you log in with your Sony ID to allow collaboration.

"Since I have only one aibo, I do not see a screen like ""aibo selection"" before and after logging in to allow cooperation, and the connection is completed as it is, but will a screen like ""aibo selection"" be displayed if I log in multiple heads?"

A) The "aibo Select" screen will be displayed, and only one of the permitted information (deviceIDs) will be received when redirecting.
Or
B)The aibo Select screen does not appear.Based on the information (such as deviceID) that can be obtained when redirecting after login, the developer must implement aibo selection function such as "Which aibo do you want to allow?"
Or
C)The aibo Select screen does not appear.In the case of multi-headed owners, all aibo have allowed collaborative apps.It is OK to register all aibo when the developer stores the individual information in the DB.
Which of these is it?

*The information access_token and refresh_token that you can get when you redirect after logging in to the developer side is not per aibo, but per Sony ID = per owner, so I think it's C.

Actually, the deviceID of aibo that detected the event will be notified, so it can be individually identified, but please tell me the specifications of Sony ID authentication = when working with the linked application by the multi-headed owner.

aibo-developer

---