AI Applications
Audiences
Define who the application serves and how policies apply.
5 min read · Updated Jul 2026
Audiences are descriptive labels that document who an application serves. They help organize policies but do not sync customer identity yet.
What you will learn
- Where audiences are defined
- Difference between audience metadata and access control
- How audiences appear on applications and policies
- Future-safe naming conventions
Steps
- 1
Open Audiences
Permissions, Audiences subnav.
- 2
Create audience
Add Nintendo customers with description External support chat users.
- 3
Assign to application
Open Nintendo Support Assistant settings, link audience metadata.
- 4
Document intent
Add note that identity sync is not yet connected; policies still use collection scopes.
- 5
Mirror internal audience
Add Nintendo employees for Internal Copilot.
- 6
Review Access Matrix
Confirm policies reference intended audience labels for operator clarity.
Common issues
- Expected per-user restriction by audience.
- Enforcement is via collections and policies today, not live identity sync.
- Duplicate audience names.
- Merge labels to keep Permissions readable.
Related glossary terms
Ready to try it in Wiki?
Start with a Wiki account and set up your Nintendo workspace today.
Was this helpful?