Sharing Agents
Agent sharing enables you to distribute agent templates to other tenants or users for their own building and customization journey. Whether collaborating with your team, delivering solutions to clients, or contributing to the broader community, sharing provides the foundation for others to build upon your work.Looking to give users access to interact with your agent? That’s handled through Agent Interfaces.
What Gets Shared
When you share an agent, you’re sharing the agent template - the building blocks others need to create their own version:- Agent configuration, prompts, and instructions
- Variables and customization options
- Tool integrations and flow logic
- Interface settings and deployment patterns
Security: Sensitive data stored as credentials is automatically replaced with placeholders. However, you must manually review your agent before sharing to protect:
- Sensitive information in Python code blocks
- Hard-coded values in user-defined tool properties
- Tool configurations that don’t utilize credentials for storing sensitive information
Sharing Methods
The Airia platform offers two distinct approaches for sharing agent templates, each designed for different distribution needs:Direct Sharing
Direct control over template distribution through private links or file export. Private Share Links generate secure, one-time use URLs that expire in 7 days - perfect for quick, tracked sharing with specific individuals. No file downloads required. Export to File creates portable JSON files you can distribute through any method - ideal for offline transfers, backups, air-gapped environments, or when you need complete control over the distribution channel. Learn more about Direct Sharing →Community Sharing
Contribute templates to the public Airia Community after review. Make your agent templates available to the entire Airia ecosystem through the Community platform. Templates undergo a review process (typically 5-7 business days) before becoming publicly available to all users. Learn more about Community Sharing →Choosing the Right Method
Select the sharing approach that best fits your use case:| Method | Use Case | Distribution | Access Control | Best For |
|---|---|---|---|---|
| Private Share Links | Quick, secure sharing | Direct URL | One-time use, expires in 7 days | Sharing with specific individuals or teams |
| Export to File | Offline/manual transfer | File download & upload | Manual distribution control | Backups, air-gapped environments, client deliveries |
| Community Sharing | Public contribution | Community platform | Public access after review | Sharing with broader community, templates |
Getting Started
Choose the approach that best fits your needs:- Direct Sharing - For controlled distribution using private share links or file export
- Community Sharing - For broader community impact and public collaboration
Frequently Asked Questions
Can recipients modify the agent template I share?
Can recipients modify the agent template I share?
What should I do if my export or share fails?
What should I do if my export or share fails?
How do I give users access to interact with my agent without sharing the template?
How do I give users access to interact with my agent without sharing the template?
If you want users to interact with your agent (chat, submit requests, etc.) rather than receiving the template for building, use Agent Interfaces instead.Interfaces allow you to expose agent functionality through:
- Chat interfaces for direct conversations
- API endpoints for programmatic access
- Slack bots, browser extensions, and other deployment methods
How can I help others understand my agent when they receive it?
How can I help others understand my agent when they receive it?
Make your agent template easy to understand and customize by documenting it properly:Annotations (Notes) on the Canvas - Add notes directly to your agent canvas to guide recipients:
- Explain the purpose of specific sections or logic flows
- Highlight setup requirements or dependencies
- Call out areas that need customization
- Provide context for complex decision points
- Overall purpose and use cases
- Required credentials or integrations to configure
- Variables that should be customized
- Expected behavior and example interactions
- Any limitations or special considerations
