I created a test account: firstname.lastname@example.org on the Alexa Skill console and a test account: email@example.com on AWS. And set up a client (client id: 1hn3j9i9thj4m85besatbhv7ko) in Cognito on AWS to combine with the Alexa Skill (id: amzn1.ask.skill.96ea45e6-a788-4dd7-acdb-847e455f4b5c) Account Linking. Using the Alexa app to enable Alexa Skill, the registration page provided by Cognito will appear. After completion, Cognito will create a set of registration information. When Alexa makes a voice request, the information that Alexa sends to Lambda will have session.attributes content. (alexa-test.png), which contains the registration information, so Lambda can confirm what user is requesting based on this information. The same configuration is set in the company's account: firstname.lastname@example.org's Alexa Skill (id: amzn1.ask.skill.18602353-3533-4473-abdd-5deacf9e1c0d) and AWS account id (049545553306) for Cognito's client (id : 1jien2pa3eqdj9dcsbbvdspa63) is established, there will be a registration page after Enable Alexa Skill, and registration information will be created in Cognito after a successful registration, but when making a voice request, the information that Alexa sends to Lambda will not have the content of session.attributes (alexa-real .png), so Lambda can’t confirm which user requested it. May I ask what is the difference between the two account settings and how can they be the same as the test account? As in receiving session.attributes using the company's account.