Govern
Policies
Policies are the business rules Novie Control checks on every request: which models, which approvals, how much funding. Write them in the Policy centre.
The Policy centre (Governance → Policies) is where you write the business rules that sit on top of roles and permissions. One policy check is used everywhere, so the same rule behaves the same way in the web app, the AI gateway and the MCP gateway.
What policies control
| Area | Examples |
|---|---|
| Models | Which models or model groups a department or workload may use. |
| Approvals | Which workload creations need a reviewer, and which are auto-approved. |
| Funding | Whether automatic top-ups are allowed, single-top-up limits, rollover and balance caps. |
| MCP | Which MCP tools may be called. |
| Reporting | Whether prompt content is collected for a scope, and for how long. |
Rules, groups and attachment
A policy is a set of rules. Each rule names an action, optional conditions and an effect (allow, deny or require approval). Rules can be combined into groups with all of / any of logic, and policies are attached to the organisation, a department or a workload. Novie shows where a policy can be attached and previews the impact before you change one.
Inheritance
Policies are evaluated from the organisation root down to the target. Deny wins over approval, approval over allow. A child can only make restrictions tighter. Novie blocks changes that would leave a running workload with no usable model, and shows the impact of removing a model before you confirm.
Drafting policies in plain language
Describe what you want, for example "Marketing can only use the cheaper model group, and any new workload over $500 needs finance approval". Novie turns this into a typed, reviewable draft, asks for clarification when the request is ambiguous or conflicts with an inherited rule, and evaluates the draft before you publish it. Nothing is published without an explicit, authorised confirmation. English and Chinese are supported.
Presets and testing
Start from presets for common setups, and use Test to see how a rule would decide a given request before it goes live.