Share Agents Across Your Team

Before You Start

Use a Team workspace when teammates need to work from the same agents, tools, schedules, traces, and workspace context. A trace is the step-by-step run log for an agent request. Create the Team workspace first so the agent belongs to the shared workspace instead of one person's personal workspace.

Team owners can invite and remove members. Members can use team agents and shared workspace resources after they accept the invite. For personal agents outside a Team workspace, only the agent owner can turn sharing on or off.

Before inviting more people, review the agent instructions, connected apps, memories, schedules, and approval rules. Share only agents your team is allowed to use with the data and tools already attached.

Open the Right Workspace

Switch to the Team workspace that should own the agent. Check the active workspace name before you create, edit, or share anything.

If the agent already lives in a personal workspace, recreate it in the Team workspace or ask your Super Agent to create the team version with the same role, instructions, and approved tools.

Invite Teammates

Open Team settings and invite each teammate by the email address they use for Agentic Workers. Ask them to accept the invite while signed in with that same email address.

Tell each teammate which Team workspace to select and which agent to use first. If they belong to several workspaces, they must switch into the Team workspace before they can see shared agents, traces, integrations, or schedules.

Start with the smallest group that needs the workflow. Add more teammates after the first shared runs behave correctly and the approval rules are clear.

Share or Use the Agent

Agents created inside a Team workspace are available to accepted team members. Teammates can open the agent from the Agents page, start chats, use connected tools that the workspace has authorized, and inspect traces for runs they can access. A trace is the step-by-step run log for an agent request.

If you use a personal share link instead of a Team workspace, open the agent from the Agents page and use the Share control. Agentic Workers copies a link to /shared-agent/[slug]. Recipients sign in, view a limited preview, and start by copying the shared agent into their own workspace.

Do not use a personal share link for internal production access when teammates should share the same history, tools, schedules, billing, and ownership. Use a Team workspace for that.

Confirm Access

Ask one invited teammate to switch into the Team workspace, open the shared agent, and run a small read-only prompt. Confirm the agent uses the expected instructions and connected app account.

Open the latest trace after the test. Check that the run belongs to the Team workspace and that any approval prompt appears before messages are sent, records are changed, or credits are spent on larger work.

Remove or Change Access

To remove team access, open Team settings and remove the member. This stops their access to the Team workspace, including team agents, shared traces, integrations, schedules, and workspace settings.

To stop a personal shared-agent link, turn off sharing from the agent owner account. Existing copied agents in recipient workspaces are separate copies, so review sensitive instructions or tools before you share.

When a teammate changes roles, review agent memories, schedules, connected apps, and approval rules. Remove access your team no longer needs and rotate provider credentials if your security policy requires it.

Troubleshooting

If a teammate cannot see an agent, confirm they accepted the Team invite, signed in with the invited email address, and switched to the correct Team workspace.

If the agent opens but a tool is missing, reconnect the integration in the Team workspace and confirm the tool is enabled for that agent.

If a personal shared-agent link does not work, confirm the owner has sharing enabled and that the recipient is signed in. If sharing was turned off, send a new link only after access is approved again.

If the agent uses the wrong context, check whether the teammate is in a personal workspace instead of the Team workspace. Move the workflow back to the Team workspace before running production tasks.