Before you start
Use an organization account and non-sensitive test data. You need permission to manage teams and roles, assign the worker’s manager, and manage its access. If a control is read-only, ask the person with that specific permission to complete the step. Have an AI Employee available and choose three test members: an intended user, a teammate without the required role, and someone outside the team. None should be the worker’s manager or a broad employee administrator.Create the team

Creating a team with synthetic Storybook example data.
Create a narrowly scoped permission role
- Choose Team role, not Organization role, then Continue.
- Name it Support colleague. Describe when it should be assigned, then continue.
- In Choose capabilities, open the Employee category.
- Select View employee, Chat with employee, and Request work.
- Leave unrelated capabilities unselected and choose Create role.

Choose Team role to keep the assignment scoped to a team. Synthetic example data.

Select the three capabilities needed for this example. Synthetic example data.
Add members and assign their team roles

Open Customer operations to manage its people. The local synthetic fixture uses the Support colleague role from this tutorial.

Choose Support colleague for Casey inside Customer operations, then save the membership changes. Synthetic example data.
Restrict the worker's audience
- Choose the accountable manager who should own configuration and approvals.
- Under Access, choose Customer operations rather than everyone in the organization.
- In the role selector, choose Support colleague rather than Any compatible role.
- Leave Share conversations across members off for this pilot.

The synthetic tutorial fixture shows Customer operations with Support colleague, private conversation context, and no additional editors.
Limit who can change the worker
Set conservative connected-tool and messaging policies
- Set Inbound Access Policy to Account Members for the pilot. This is a channel rule, not a replacement for the worker’s internal team audience.
- Set Tool approval policy to Approval-first while testing.
- Set Outbound Messaging Policy to Ask every time, or Disabled if no outbound messaging is needed.
- Review and remove saved allow exceptions that would undermine the pilot’s review policy.
Verify allowed and denied behavior
Use separate member sessions. Do not verify everything while signed in as an administrator.Move from pilot to production
- Record the manager, intended audience, editor areas, approved connections, and any saved exceptions.
- Re-run the tests after changing roles, team membership, worker governance, or tool policies.
- If you later choose Recommended tool approvals, test the exact operations you intend to allow; drafts and some low-risk actions can be treated differently from ordinary writes.
- Review membership and exceptions periodically. Removing a team assignment does not remove an unrelated organization-level grant.
- During handovers, reassign the manager and review unattended work and credential scope. See Manager responsibilities.

