Getting started
Your first policy
Set knowledge access boundaries for your AI Application.
7 min read · Updated Jul 2026
Policies define what knowledge an AI Application may retrieve and how it should behave when content is missing or sensitive.
What you will learn
- Where policies live on an AI Application
- How allow and deny scopes work on collections
- How to require verified documents only
- How to test policy effect in Access simulator
Steps
- 1
Open the application
Go to AI Applications and open Nintendo Support Assistant.
- 2
Open Permissions tab
Click the Permissions tab on the application detail page, or open Permissions in the sidebar and filter by this application.
- 3
Review collection scopes
Confirm Allow rules for Nintendo Help Center and Nintendo Refund Policy. Add Deny for any internal collection that should never surface.
- 4
Add verification scope
Add a scope that allows only documents with verification status Verified or Review due within policy limits.
- 5
Set escalation behavior
Configure refusal rules for billing disputes so the assistant escalates instead of improvising when policy passages are missing.
- 6
Activate the policy
Set policy status to Active. Draft policies do not affect Answer Playground runs.
- 7
Run Access simulator
Open Access simulator from the application menu. Test retrieval for a public article and an internal document to confirm deny behavior.
Common issues
- Policy shows conflicts with template defaults.
- Resolve duplicate scopes by removing overlapping deny and allow rules on the same collection.
- Verified documents still blocked.
- Check lifecycle status. Published and verified are both required unless your policy explicitly allows needs review.
Related glossary terms
Ready to try it in Wiki?
Start with a Wiki account and set up your Nintendo workspace today.
Was this helpful?