Know which user or service is requesting the action.
One Core. Reused Across Every Product.
A shared platform for intelligence, integrations, workflows, management views, agent creation and enterprise control—reused across Business AI, Design & Build, Real Estate, Construction, Finance and Workforce.
From question to controlled business action.
The operating pattern separates understanding and recommendation from permission checks and sensitive execution.
Use the right model for the right job.
The platform architecture can route model requests based on configured provider availability, use case, data class, cost, speed and evaluation results. Provider support depends on the deployed integration.
Model providers / model classes
Names represent integration targets in the platform architecture; each provider must be configured and approved before use.
Routing considerations
- Accuracy and evaluation results
- Cost and token / request limits
- Latency and availability
- Use-case capability
- Data classification and governance
- Fallback and operational policy
SN Shield keeps policy around the AI layer.
Authentication, permissions, business rules, approvals and audit data should remain server-side and independent from prompt instructions.
Check access to modules, data and actions on the server.
Apply thresholds, policies and required conditions.
Require explicit review for sensitive operations.
Only approved tools can perform production actions.
Record the request, decision, outcome and relevant references.