Skip to main content
Use this checklist with your security owner and the accountable manager of each production AI Employee. A configured control is not the same as a tested control: record what you inspected, the identity used, the expected result, and what happened.

Review the security boundaries

Use Create a team-restricted AI Employee, Read-only Finance worker, and Manager handover as worked examples.

Know what Activity can establish

The Activity Log helps authorized users review worker conversations, tasks, workflows, and service events. Use it alongside task details, approval requests, and your provider’s own records to investigate what happened. Do not treat the worker Activity Log as proof that:
  • Every denied access attempt, browser action, or network request is recorded there.
  • All records have a particular retention period, immutable storage, or a security-export format.
  • A missing activity item means an external action could not have occurred.
  • A completed task alone proves that every provider-side change succeeded exactly once.
Activity access and export are separate capabilities. Grant them only where needed, and confirm available export controls and record coverage before including an export in an audit process.

Request deployment-specific evidence

For controls your team cannot verify from the product UI, coordinate a review through the Trust Center or support@odella.ai. Ask for the applicable, current evidence for:
  • Worker and browser isolation, network access, and any private-connectivity requirements.
  • Data residency, international processing, and customer-selected providers.
  • Platform security logging, available customer audit evidence, retention, and incident support.
  • Backup, recovery, deletion, and assurance commitments that apply to your agreement.
  • The exact supported scope of approval and revocation controls for your use case.
Product source, screenshots, and architectural descriptions explain design; they do not replace deployed verification or contractual commitments. Do not infer universal zero-egress execution, comprehensive data-loss prevention, or per-click browser approval from a general security description.

Maintain a review record

For each important control, record:
  1. Claim: What restriction or behavior your organization needs.
  2. Scope: Worker, team, connection, provider identity, and operation covered.
  3. Owner: Who maintains the configuration and approves changes.
  4. Evidence: Configuration reviewed, test performed, result, and date.
  5. Exception: Any unresolved limitation and the decision to avoid, mitigate, or accept it.
  6. Recheck trigger: Role changes, new tools, provider-scope changes, manager transfers, and product changes.
Keep secrets, private approval links, and unnecessary customer data out of this record. Review it on your organization’s schedule and after consequential changes. For legal and assurance resources, see Security and data protection.