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.
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.
Maintain a review record
For each important control, record:- Claim: What restriction or behavior your organization needs.
- Scope: Worker, team, connection, provider identity, and operation covered.
- Owner: Who maintains the configuration and approves changes.
- Evidence: Configuration reviewed, test performed, result, and date.
- Exception: Any unresolved limitation and the decision to avoid, mitigate, or accept it.
- Recheck trigger: Role changes, new tools, provider-scope changes, manager transfers, and product changes.

