What deterministic governance means
For supported connected tools, Odella uses explicit policy evaluation to allow an action, block it, or require approval. The worker cannot grant itself permission by saying an action is safe. The decision uses the resolved tool, its classification, configured policy, and saved exceptions. Unknown connected-tool actions ordinarily require approval under the recommended policy. Explicit blocks take priority over allow exceptions; credential and administration actions classified as credential operations are blocked by this policy. Deterministic does not mean infallible. Tool classification is not proof of what a third-party service actually does. Review the exact tool and provider permissions, especially for custom integrations.Separate the control layers
Isolated execution and zero-trust principles
Treat the worker’s execution environment as a limited participant, not as a trusted administrator. A running AI Employee does not inherit unrestricted access to the organization. Platform requests carry identity and account context, and connected applications and model access use controlled service boundaries. Odella separates worker execution from the public application. The Kubernetes worker configuration includes non-root execution, a read-only system filesystem, disabled privilege escalation, dropped Linux privileges, and resource limits. Writable workspace and temporary areas remain available for legitimate work. These are complementary boundaries: a workspace is not the authorization authority, and a worker’s request is not itself permission to access a platform resource. Model-provider credentials are handled at a controlled service boundary rather than provisioned as direct provider keys in the worker’s workspace.Connected-tool approvals
Open AI Employee → Settings → Security & Privacy to choose a tool policy and review saved rules.- Use Approval-first during a sensitive pilot so ordinary connected reads and writes require review.
- Use Restricted when ordinary connected writes should be blocked rather than offered for routine approval.
- Review saved Always allow exceptions; they can change the behavior you expect from the default policy.
- Use explicit Always block rules for tools the worker must not use.
- Prefer provider accounts with narrow permissions. An approved tool can still have broad access at the provider.
Browser work is a different boundary
Browser access and connected-tool access are not interchangeable. A website button is not automatically subject to the connected-tool approval matrix.Public-page and workspace browsing
The workspace browser supports public-page work and local rendering. Its enforced checks include command validation, separation of workspace browser targets, restrictions on unsupported navigation schemes, and checks against direct navigation to common local, private-network, and cloud-metadata addresses. For local files, browser navigation is restricted to supported file types inside the worker’s workspace, with checks against sensitive locations and paths that resolve outside it. Public-site browsing also has bounded tab, navigation, and action budgets. It stops for detected visible password or one-time-code fields and supported challenge pages. A top-level access denial or rate-limit response restricts further browsing of that origin. These are safeguards, not a complete network filter or credential-leak prevention system. They do not justify promising that every redirect, page subresource, site action, or possible data transfer is blocked.Signed-in browser work
Signed-in browsing uses a separate browser environment associated with the authenticated user’s account and identity. That user’s AI Employees can share that browser context. A run without the required user identity does not receive that user’s private browser through the remote browser command boundary. This distinction matters: a private browser is user-scoped, not a separate login vault for every worker. Grant access to sensitive sites deliberately, use restricted website accounts, and review saved sign-ins in Vault. For website identity selection, saved-session removal, downloads, and safe tests, see Signed-in browser security.Example: draft customer replies without broad access
- Limit the worker’s internal audience to a customer-service team and qualifying role.
- Give only the manager or designated editors permission to change tools and approvals.
- Connect a test support account with the minimum provider permissions.
- Start with Approval-first, review saved exceptions, and use Ask every time for supported outbound messaging.
- Ask the worker to read a test record, draft a reply, and attempt a record update. Verify the actual review behavior for each operation.
- If the work requires a signed-in website, review that website account separately. Do not rely on connected-tool approvals to gate website mutations.
Questions for a security review
Ask Odella to confirm requirements that are specific to your deployment or agreement:- Network destinations and any private-network connectivity requirements.
- Isolation, regional processing, and third-party browser or model dependencies.
- Which exact tool and browser operations require human review.
- Credential scope, saved website sessions, retention, and revocation behavior.
- Available security evidence and audit records beyond the worker Activity Log.

