 Although it's currently not possible to add multiple audience values to an access token in Customer Identity Cloud, it is possible to configure a single logical API to encapsulate multiple distinct API implementations. We're answering frequently asked questions from the Octa Customer Identity Cloud community. In this video, I'll be walking through a few steps that you can take to configure a logical API that will work to control access to multiple APIs with a single authorization flow. Before watching this video, it would be beneficial to have a basic understanding of the concept of an audience, OAuth, OIDC, and APIs in general. You'll also need an application created in your dashboard as well as a test user to log into this app. In this case, I'm using a spa that I've created previously. Alright, let's go ahead and get started. First, you'll need to create and configure an API which will represent your logical API and your dashboard. Take note of the API identifier from the Settings tab. You'll need that shortly. Next, you'll need to add permissions to this API, one for each distinct API implementation. In this case, I've created two permissions. One to represent a calendar API and the other represents a contacts API. We'll take advantage of the Authentication API Debugger tool to see what this looks like in action. You can find this tool by clicking extensions on the left-hand side of the dashboard and searching for it. And that's all there is to it, just to quickly recap what we accomplished here. First, we created the logical API in the dashboard. Next, we added two permissions, Read Contacts and Read Calendar. Each of these represents a unique API implementation. We then took a look at the Authentication API Debugger tool, which allowed us to test this flow. Upon successful authorization, we were able to see the user access token with the necessary scopes. And that's it. If you found this video helpful, please like and subscribe on YouTube and join us for more content at community.auth0.com.