Customer-defined boundaries
Decide what Groviqo may do.
Choose an operating mode, enabled actions, approval requirements and risk limits. Supported execution remains subject to scope, permissions, cost estimates and provider capability.
Runtime Governance & Policy Boundaries
PostgreSQL RLS, FinOps caps, and human sign-off gates enforced at runtime.
Illustrative choices only. This is not a live customer policy.
| Action | Example permission |
|---|---|
| Read data automatically | Allowed within source permissions |
| Create recommendations | Allowed |
| Create drafts | Allowed; no publishing |
| Modify metadata | Approval required |
| Publish blog articles | Approval required |
| Submit IndexNow | Allowed with a supported path |
| Modify production code | Approval and supported integration required |
| Delete content | Never under this example policy |
| Run a high-risk migration | Never automatically under this example mandate |
Product settings cover mode, actions, approvals, risk, blast radius and spend cap. Estimated cost is checked against the cap. Saves are scoped to tenant, workspace or site and audited with a reason and version.
Execution also requires permissions and provider capability. Migration needs a supported workflow and human approval. Runtime deletion is configurable and can require approval; the prohibition here is this customer example.
How the capability works
A customer policy example
These nine choices illustrate a customer mandate, not a live policy or a promise that every action is available. Actions need a supported execution path and the appropriate permission.
- Read data automatically — allowed within authorized source access
- Create recommendations — allowed
- Create drafts — allowed; drafts do not authorize publishing
- Modify metadata — approval required
- Publish blog articles — approval required
- Submit IndexNow — allowed where a verified supported path exists
- Modify production code — approval required; execution is integration-dependent
- Delete content — never under this example policy: deletion is disabled
- Run a high-risk migration — never automatically under this example mandate; human approval and a supported migration workflow are required
Save boundaries before execution
The implemented policy settings cover mode, action types, approvals, allowed risk, per-action risk ceilings, maximum affected items and spend cap in minor currency units. Estimated cost is checked against that cap; paid actions with an unknown required estimate are denied.
- Authorized managers save policy for tenant, workspace or site scope with a reason, version check and audit record
- Policy permission does not grant provider access or create an unsupported capability
- Deletion is configurable in the runtime and can require approval; the never-delete rule above is this customer example, not a platform-wide prohibition
Follow the decision through its records
Policy saves and approval decisions have audit records. Agent Activity shows recorded reasons, evidence and outcomes; proposals, approvers, provider/model attribution and later verification may live in separate records. Missing information stays unavailable. Measured request cost is not automatically the total cost of an action.
- Review the eleven Agent Audit questions on the Security page
Practical tooling for end-to-end execution
Explicit permission to act
Enabled actions still face risk, approval, scope, budget and capability checks.
Traditional approach vs Groviqo
| Dimension / Capability | A script with broad write access | A scoped execution decision |
|---|---|---|
| Execution boundary | Write access alone does not express the customer mandate | Policy, permission, risk, approval, blast radius and spend checks |
Frequently asked implementation questions
Does allowing an action guarantee it can run?
No. Provider capability, authorization and a supported workflow must also be available. Rollback depends on the workflow and a reliable provider restore or compensation path.
Want to see what your site is missing?
Connect your domain, inspect the evidence, and use Groviqo to prioritize the next growth moves.
Start at your pace. Connect your data sources, surface high-impact opportunities, and execute improvements with total control.