Adopting approved agents
This is one of the clearest ways enterprise differs from the self-serve product. A standard user can adopt any agent they like. A team member in an enterprise adopts from the set an admin has approved — a curated shelf, not the whole store.
Why it works this way
Section titled “Why it works this way”Approval is how an organization gets the speed of a marketplace without the risk of anyone wiring up anything. Admins vet agents once — checking what they do, what they touch, and what they’re allowed to act on. Team members then move fast inside that vetted set, confident they’re using something the organization already trusts. It’s the same reason a company keeps an approved-vendor list: freedom to choose, inside a boundary someone thought about.
How a team member adopts an agent
Section titled “How a team member adopts an agent”- Open the Marketplace. You’ll see the approved catalog for your team, not the entire public marketplace.
- Choose an agent and review what it does, the tools and connectors it uses, and any approvals its actions require.
- Adopt it. It moves into your Workspace, ready to run.
When the one you need isn’t approved
Section titled “When the one you need isn’t approved”If you need an agent that isn’t in the approved set, you can request it. The request routes to an admin, who can approve it for you — and often for the whole team, so the next person doesn’t have to ask. See Requests.
A quick example
Section titled “A quick example”A new marketing hire wants an agent that drafts social copy. It’s not in their team’s approved set yet, so they request it. Their admin reviews it, confirms it only uses approved connectors, and approves it for the whole marketing team. Now it’s on the shelf for everyone — vetted once, reused by many.
Related
Section titled “Related”- What admins approve and how → Governance & Approvals
- Publishing your own agent for others → Publishing an Agent