After reading through the limited documentation on help.apple.com, i stumbled across the following:You must register and verify all top-level domains and subdomains where you will display the Sign in with Apple button. Domains are associated with your Apple Developer Team ID. As a result, you cannot register the same domain with a different Team ID.This can be found under the Troubleshooting Domain Verification section of the following page: https://help.apple.com/developer-account/?lang=en#/dev1c0e25352.This poses a problem for my organisation since we operate to completely separate platforms from mydomain.com that do not share the same mobile applications nor do they share the same authentication system. Since the application I work on is hosted by a different developer account (and therefore a different Team ID), i would prevent our other product from ever being able to adopt Sign in with Apple if I was to verify the domain against my team.From our testing, we're able to implement the sign in flow without verifying domains however this seems to go against the documentation:Now that your Apple Services ID is registered, you need to verify you own the provided domain. If the domain is not verified, the service will not function.Maybe we're missing something, but we're hesitent to verify the domain since it sounds like other reports suggest that removing a verified domain does not in fact allow a different team to go and then verify the domain in the future. I don't want mydomain.com to become linked to my teams developer account if i can't change this in the future. Esepcially because this developer account only exists because my team wasn't able to migrate an existing app (that we acquired) into the primary developer account in the first place.I am aware that we are able to implement Sign in with Apple on iOS without having to worry about verified domains, however shipping a login mechanism on a single platform and preventing users from being able to use that mechanism on other operating systems (Web or Android) goes directly against advice from Apple in the WWDC session videos as well as our desire to be able to allow our users to authenticate on any of our supported platforms. I don't want us to get to a situation where the App Store Review team reject our application in April since we don't support Sign in with Apple and i don't want for us to be foreced into rolling out Sign in with Apple on iOS only. I'd really appreciate it if anybody from Apple or anybody with experience from a similar sitatuon could help us out here since we're a bit stuck.Thanks,Liam