Models and Router
Aliases, evaluated capabilities, policy-first routing and fail-closed behavior.
Overview
Use Models and Router through visible, authorized actions. Availability depends on role, Group policy, mode and evaluated runtime configuration.
Who it is for
Use Models and Router through visible, authorized actions. Availability depends on role, Group policy, mode and evaluated runtime configuration.
Quick Start
Use Models and Router through visible, authorized actions. Availability depends on role, Group policy, mode and evaluated runtime configuration.
Main concepts
Use Models and Router through visible, authorized actions. Availability depends on role, Group policy, mode and evaluated runtime configuration.
Common tasks
Use Models and Router through visible, authorized actions. Availability depends on role, Group policy, mode and evaluated runtime configuration.
Permissions and roles
Use Models and Router through visible, authorized actions. Availability depends on role, Group policy, mode and evaluated runtime configuration.
Local / Hybrid / External
Use Models and Router through visible, authorized actions. Availability depends on role, Group policy, mode and evaluated runtime configuration.
Limits
Use Models and Router through visible, authorized actions. Availability depends on role, Group policy, mode and evaluated runtime configuration.
Security and privacy
Use Models and Router through visible, authorized actions. Availability depends on role, Group policy, mode and evaluated runtime configuration.
Troubleshooting
Record the symptom and WICSAI code, then check status, permissions and the selected route.
FAQ
Use Models and Router through visible, authorized actions. Availability depends on role, Group policy, mode and evaluated runtime configuration.
Related topics
Use Models and Router through visible, authorized actions. Availability depends on role, Group policy, mode and evaluated runtime configuration.