Skip to main content
Set boundaries before expanding responsibility

Start here before inviting colleagues, connecting real systems, or preparing a worker for production use.

Follow the team-access walkthrough →

Make three separate decisions

  1. Who can use the worker? Use teams, roles, and the worker’s primary audience. Access control.
  2. Who can change its setup? Assign a manager and selected editing areas in Governance.
  3. What may it do? Assign only necessary resources and configure tool, messaging, and approval policies.
Instructions alone do not enforce these restrictions. An approval also does not supply a missing resource permission or provider connection.

Follow a worked example

Restrict a worker to a team

Create a team and role, assign members, limit editors, and test allowed and denied access.

Set up a read-only Finance worker

Combine provider-side read access, blocked connected writes, and disabled outbound messaging.

Hand over a worker safely

Transfer accountability, review unattended work, and remove obsolete access.

Review readiness for production

Record your settings, acceptance tests, exceptions, and evidence still needed.

Understand the boundaries before relying on them

Connected-tool approvals are not a universal browser-action policy. Confirm deployment-specific guarantees through Odella’s security review rather than assuming every execution path has the same controls.