Be specific.
Define boundaries around people, teams, tools, and actions. Make Salesforce read-only while allowing a new account with manager approval.
Set what AI employees can do, who approves, and where data lives.
Rule: “Ask before deleting anything.”
Attempt in Google Drive: Delete “Q3 forecast”
Result: Needs approval
Rule: “Only talk to John, Dan and the Marketing team.”
Attempt in Slack: Reply in #marketing
Result: Allowed
Rule: “Managers approve new Salesforce accounts.”
Attempt in Salesforce: Create Northwind account
Result: Needs approval
Rule: “Never email anyone outside the company.”
Attempt in Gmail: Email jane@northwind.com
Result: Blocked
Define boundaries around people, teams, tools, and actions. Make Salesforce read-only while allowing a new account with manager approval.
Require approval for sensitive actions. An employee can prepare a change and ask before carrying it out.
Review governance decisions and approvals in the audit history, so you can understand how your rules applied.
Approve once, for an hour, or for good.
Ava asked 4m ago in Slack · 23h 56m left
Hi Maya, attached are the Q3 renewal terms we discussed. The pricing sheet covers all three tiers. Happy to walk through it on Thursday.
External recipient and an attached pricing file.
Runs this one call. Nothing is remembered: the next one asks again.
Adds a temporary allow rule for gmail_send_email that expires in an hour.
Adds a permanent allow rule for gmail_send_email to Ava’s rules. Revoke it any time in Permissions.
Blocks this call and tells Ava why, so it can try another way.
Every organization starts with baseline guardrails. Only an employee’s manager or an admin can add tools or change its policies.
Sensitive actions pause for the manager, who can approve once, allow for a while, allow permanently, or deny.
Say “stop” in the conversation and the running work halts immediately, including tools already in flight.
Untrusted content from messages, web pages, and tool results can be scored and blocked, flagged, or held for approval.
Decide who can reach each employee, internally and externally, from manager-only to specific people and channels.
Hard caps per employee and per scheduled task, daily, weekly, or monthly. At the cap, the employee stops acting.
Keys, secrets, and integration credentials are encrypted at rest with AES-256. All data in transit uses TLS.
Policy edits, credential operations, role changes, and admin actions are recorded in an append-only log that can’t be edited.
Choose the providers and models behind inference and tooling, pinned per capability, and allow only the ones you approve.
Use your own provider credentials for the organization or a single employee, so work runs under your own account and terms.
Run a dedicated data plane in your own AWS or Google Cloud account. Data stays in your region, with keys you own.
Single sign-on, groups synced from your identity provider, and role-based access for admins, managers, and members.
Native AWS, Google Cloud, and Azure connectors, checked by the same CEL policies.
CloudWatch logs, metrics, and alarms.
EKS, ECS, EC2, RDS, and Lambda.
Start, stop, or reboot EC2 and RDS.
Cloud Logging, metrics, and alert policies.
GKE, Cloud Run, and Compute Engine.
Start, stop, or reset VMs.
Log Analytics queries, metrics, and alerts.
AKS, VMs, Container Apps, and Functions.
Start, stop, or restart VMs.
Start with one role and one real task.