Publishing an agent
Building an agent for your personal use is simple. Publishing that agent, making it available for colleagues across your organization to adopt, is where enterprise governance and quality controls step in.
The publishing workflow ensures that custom-built automations can spread across teams rapidly while maintaining administrative oversight, security compliance, and operational reliability.
The administrative approval gate
Section titled “The administrative approval gate”When a non-administrative team member publishes a custom agent, it does not appear in the marketplace immediately:
- Automated review routing — publishing submits the agent configuration to an administrative queue for review. Admins work that queue in Requests.
- Security and capability check — workspace administrators evaluate the agent’s instructions, attached functions, data connectors, and action permission levels.
- Approval or feedback — the administrator either approves the asset, making it visible in the enterprise marketplace, or returns it to the builder with specific revision notes.
While workspace administrators can publish assets directly to the catalog, team members publish through this approval gate. This single structural check allows organizations to democratize automation building without risking unvetted software entering production workflows. Who holds which publishing right is set out in the capability matrix.
What to include for fast approval
Section titled “What to include for fast approval”Providing clear context with your submission helps administrators review and approve your agent quickly. A complete submission includes:
- Clear functional summary — a plain-language description of what the agent accomplishes and which operational problem it solves.
- Connected systems and data scope — a list of all enterprise tools, APIs, databases, or uploaded knowledge documents the agent interacts with.
- Action permission mapping — details on which actions are set to Allowed, Needs approval, or Blocked. See Personality and guardrails.
- Target audience scope — specifies whether the agent is intended for a single team, an entire department, or the whole organization.
Lifecycle after publishing
Section titled “Lifecycle after publishing”Once an agent is approved and published to the catalog:
- Availability — teammates within the designated target scope can view, evaluate, and adopt the agent into their own workspaces with a single click. See Adopting approved agents.
- Version control and change monitoring — depending on your organization’s security configuration, significant updates made to an agent after publishing may require a brief re-review. This prevents a published asset from quietly changing its behavior or adding unvetted system connections after it has been trusted.
- Visibility scopes — published agents can be assigned Private, Departmental, Organizational, or Public visibility, where Public means available to everyone within your own enterprise organization.
Example: vendor reporting agent
Section titled “Example: vendor reporting agent”Consider an operations lead who builds an agent to automate vendor reporting:
- Custom construction — the ops lead builds an agent that retrieves vendor delivery logs and compiles a weekly summary report.
- Publishing submission — she submits the agent to the marketplace, attaching notes confirming that the agent uses read-only connectors and posts solely to a designated internal channel.
- Administrative verification — an IT administrator reviews the submission, verifies that no high-risk write operations are enabled, and approves the request.
- Immediate team adoption — by that afternoon, the agent appears in the operations team’s marketplace catalog, allowing three other managers to adopt the tool for their own vendor groups.
Publishing workflow summary
Section titled “Publishing workflow summary”| Stage | Action required | Primary goal |
|---|---|---|
| Creation | Build, test, and verify agent in personal workspace | Ensure task accuracy and reliable performance |
| Submission | Submit for publishing with functional notes and scope | Provide IT admins with required review context |
| Review | Admin evaluates connectors, guardrails, and tools | Verify security compliance and data safety |
| Distribution | Agent goes live in the enterprise marketplace catalog | Enable team-wide adoption and compound value |
Next steps
Section titled “Next steps”- Manage approval queues and incoming requests → Requests
- Understand permission roles and publishing rights → Capability matrix
- Learn how team members adopt approved assets → Adopting approved agents
- Browse what is already published → Agent marketplace
- Roll adoption out across the organization → Marketplace adoption