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
- Who can use the worker? Use teams, roles, and the worker’s primary audience. Access control.
- Who can change its setup? Assign a manager and selected editing areas in Governance.
- What may it do? Assign only necessary resources and configure tool, messaging, and approval policies.
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.

