Skip to main content
Odella separates who may use an AI Employee, who may change its settings, and what the worker may do. Configure all three; instructions such as “only help Finance” are not a substitute for access controls.

The access-control vocabulary

A resource’s audience and explicit grants form its access control list (ACL). Roles describe permitted operations; resource rules determine where those permissions apply. Access is evaluated for the requested operation, not merely whether a button is visible.
An AI Employee’s job title or responsibilities are not an organization permission role. Assign permission roles to people, then select the appropriate audience and role requirement on the worker.

Example: a team-limited worker

Suppose the primary access rule is Customer operations with Support colleague:
  • A Customer operations member holding that role in that team can use the worker according to the role’s capabilities.
  • A member of another team does not qualify merely because they hold a role with the same name.
  • Team membership alone does not satisfy a specific required-role rule.
  • Viewing, chatting, requesting work, and viewing activity are separate capabilities. Do not grant activity access simply because someone needs to chat.
  • The accountable manager and people with broad employee-administration access retain applicable access. A team restriction is not a way to exclude those administrators.
Review other grants and higher-privilege roles before claiming that a worker is accessible “only” to a particular group.

Access does not imply editing

In Settings → Governance, choose who may edit and which areas they may change. A colleague might be allowed to update Working instructions without being allowed to change Sending & approvals or Who can contact the Employee. Worker-specific configuration permissions are managed through Governance, not by adding those configuration capabilities to a general organization role. An editor must also have access to the worker; selecting someone as an editor does not itself add them to its audience. The manager relationship is separate again. Read Manager responsibilities before assigning or transferring it.

Permission to ask is not permission to act

A person authorized to request work has not thereby authorized every external action needed to finish it. For example, a colleague can ask a worker to update a customer record, but the work still depends on:
  1. The worker having the necessary connected tool and resource assignments.
  2. The applicable user or account connection being available.
  3. The provider account having permission to update that record.
  4. The connected-tool policy allowing the operation or receiving the required approval.
  5. Any separate outbound-recipient policy and workflow review steps.
An approval does not supply missing resource access or a missing provider connection. A connection does not override worker governance. See Credentials and user scope and Tool and browser boundaries.

Troubleshoot an unexpected result

Test with ordinary members, not only administrators. For a complete setup and a positive/negative test matrix, follow Create a team-restricted AI Employee.