Security
Workspace isolation
How knowledge stays scoped to each workspace.
5 min read · Updated Jul 2026
Each workspace is isolated. Members only see workspaces they are assigned unless they are organization admins.
What you will learn
- Workspace boundary rules
- Cross-workspace access for org admins
- Data residency notes at plan level
- Implications for multi-product orgs
Steps
- 1
List workspaces
Organization Workspaces page shows separate Nintendo and other products.
- 2
Verify member scope
Members page confirms user lacks access to unrelated workspaces.
- 3
Test switcher
User should only see assigned workspaces in switcher.
- 4
Separate AI apps
Nintendo Support Assistant cannot retrieve another workspace collections.
- 5
Document policy
Record which workspace holds customer versus internal data.
Common issues
- Admin sees all workspaces.
- Expected for org admins; use member role for restricted access.
Related glossary terms
Ready to try it in Wiki?
Start with a Wiki account and set up your Nintendo workspace today.
Was this helpful?