> For the complete documentation index, see [llms.txt](https://docs.taskade.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taskade.com/community-and-sharing/community-and-sharing.md).

# Community & Sharing

Share, publish, and clone Taskade apps and templates — collaborate with your team or ship to the community with public links and custom domains.

**Share the Taskade Genesis apps that you build. Find apps from other builders, and copy a complete app with one click.**

{% hint style="success" %}
**What you can do here.** Publish your Taskade Genesis apps to the community. Let others copy them with **Let others clone**. Sell original apps as paid App Kits.
{% endhint %}

***

## **Publish and Share Your Apps**

You can publish your Taskade Genesis apps and let other people clone them.

### **Publishing Apps**

A published app has a link. You choose who can open it.

**What you get when you publish:**

* **Direct access**: Users open your app at its own URL.
* **No installation**: The app works in any browser.
* **Version control**: You can update your published app and keep the same link.
* **Sales**: You can sell an original app as a paid App Kit for a one-time price.

**Publishing options:**

* **Public apps**: Anyone with the link can open them. Search shows them only when **Show in public listings** is on.
* **Private apps**: Each person signs in, or types one shared password (Pro and up).

### **App Visibility Settings**

In the **Publish** panel, choose who can open your app under **Who can open it**.

**Public apps:**

* Anyone with the link can open and use your app.
* Visitors do not sign in.
* Good for marketing, demos, and free tools.

**Private apps:**

* Each person signs in (**Each person signs in**, on every plan), or types one shared password (**Anyone with the password**, Pro and up).
* You control who can use your app in the **App Users** tab.
* Good for client portals and internal tools.
* Sign-in confirms who a visitor is. It does not hide other people's records. To show each person only their own rows, turn on **Private entries**.

### **Unpublishing Apps**

You can unpublish your app at any time:

1. Open your Taskade Genesis app in your workspace.
2. Click **Publish** in the top toolbar.
3. Click the arrow on the **Live** button at the bottom of the menu.
4. Click **Unpublish app**.

**Note:** Public access stops at once, and the URL stops working. Users who saved the link cannot open the app.

### **Enabling Cloning (Forking)**

You can let other people copy your published app into their own workspaces:

1. Open **Publish → Let others clone**.
2. Choose **Free** or **Paid**. **Off** stops new clones.

A public listing alone does not make an app cloneable. When other people copy your public app, the copy is a **fork**. A **clone** can also mean a copy of your own app inside your workspace, made with **Duplicate app**.

**What a clone gives:**

* **One click**: Users clone your whole app with one click.
* **Full copy**: Taskade copies the projects, agents, automations, and media files. Taskade does not copy connected accounts and secrets.
* **Independent app**: The cloned app works on its own.
* **Free changes**: Users can change their copy. The original app does not change.

### **When to Use Templates vs. Cloning**

**Use a template when:**

* You give people a starting point that they change.
* Users must change the app a lot for their use case.
* You share an example workflow that is not finished.

**Use a clone when:**

* Your app is a complete, working solution.
* Users must get working functions with no setup.
* You share a workflow that works in production.

## App Forking

The fastest way to learn and build is to start with a working app. With Taskade Genesis, you can fork a community app when its creator turns on **Let others clone**.

### **What is App Forking?**

A fork is a complete, independent copy of a Taskade Genesis app in your workspace. A fork gives you more than a simple template:

* **Full copy of the workspace parts**: projects, agents, automations, and media files
* **Ready workflows**: the automations arrive set up. Connect your own accounts, because Taskade does not copy connected accounts and secrets.
* **Full rights to change**: change, rebrand, and extend the app
* **Independent copy**: your fork changes separately from the original

### **One-Click Complete Duplication**

When you fork a Taskade Genesis app, you get:

| What Gets Copied       | Details                                                                                                                                |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **🎨 App Interface**   | The full layout, styles, and user experience                                                                                           |
| **📊 Projects & Data** | Project structures and data. Visitor submissions stay out. A project shipped as sample data brings only the creator's own example rows |
| **🤖 AI Agents**       | Trained agents with their knowledge and personalities                                                                                  |
| **⚡ Automations**      | Workflows. Connect your own accounts                                                                                                   |
| **📁 Media Files**     | Images, documents, and assets                                                                                                          |
| **🔧 Configuration**   | Settings, data access choices, and customizations. **Invite only** sign-up and **Private entries** carry over                          |

A project where each person sees only their own entries never ships its rows. Sign-in alone confirms who a visitor is. It does not hide other people's records. Test your copy with a second account before you share it.

### **Professional Use Cases**

**For agencies:**

* Fork a client portal template and change it for each client.
* Start with a working solution, not a blank app.
* Keep the same quality across client projects.

**For entrepreneurs:**

* Copy a working business model and change it for your market.
* Learn from working examples of complex workflows.
* Launch faster on a tested base.

**For teams:**

* Share internal tools across departments.
* Make processes the same with working templates.
* Let team members who do not code put solutions to use.

***

## Sharing Your App with Everyone

### What Happens When You Share?

When you share your Taskade Genesis app with the community, it goes into a public library. Other business owners can find it, try it, and copy it. Explore the Taskade App Factory at [taskade.com/apps](https://www.taskade.com/apps) to see the apps that other builders published. Your shared app helps other people and shows your skills.

### When to Share with Community

**Good to share:**

* General business solutions (CRM templates, feedback systems, inventory trackers)
* Educational examples and tutorials
* Industry tools that help many organizations
* Apps that show your skills and ideas
* Apps that build your professional reputation

**Keep private:**

* Client solutions with private workflows
* Apps that contain sensitive business data or processes
* Highly custom solutions that do not work for other people
* Apps that are not ready for public use

***

## **Professional Publishing with Paywalls**

You can sell your Taskade Genesis apps.

### **Monetize Your Expertise**

To sell a Taskade Genesis app:

1. Open **Publish → Let others clone**.
2. Choose **Paid**.
3. Set a **one-time price**.
4. Click **Put on sale**.
5. Finish the payout setup in **Earnings**.

Buyers pay to get their own private copy of the app. Read [Paid Apps](https://docs.taskade.com/community-and-sharing/community-and-sharing/publish-and-clone.md#paid-apps) for the full flow.

### **Perfect for:**

**Consultants and agencies:**

* Client assessment tools and calculators
* Industry templates and workflows
* Diagnostic and analysis apps

**SaaS entrepreneurs:**

* Small business tools for one market
* Special dashboards and reports
* Process automation solutions

**Content creators:**

* Educational tools and courses
* Interactive guides and tutorials
* Community management apps

### **Professional Features**

| Feature                   | Benefit                                          |
| ------------------------- | ------------------------------------------------ |
| **🔒 Access Control**     | Buyers get their own private copy of the app     |
| **📊 Analytics**          | Built-in counts of views, likes, and installs    |
| **💳 Payment Processing** | Taskade runs the checkout and the payouts        |
| **🎨 Custom Branding**    | Your logo, colors (Business+), and domain (Pro+) |

***

## **Embeddable Public AI Agents**

You can put your trained agents into websites, documentation, or other web pages.

### **Agents Anywhere**

The **Share** panel of an agent has an embed snippet builder. Copy a ready-made snippet: an inline iframe or a floating chat widget. You can change the **launcher icon** and the background to match your site. The iframe points at the public URL of your agent:

```html
<iframe src="https://www.taskade.com/a/your-agent-id"
        width="600" height="400"
        frameborder="0"
        allow="clipboard-read; clipboard-write"
        allowfullscreen>
</iframe>
```

Copy the snippet from the Share panel. Do not write it by hand. The builder adds the correct URL for your agent, custom domains included.

### **Use Cases**

**Customer support:**

* Put support agents on your website.
* Answer questions at all hours with your product knowledge.
* Answer common questions automatically.

**Lead generation:**

* Use agents that qualify possible clients.
* Hold interactive consultations that collect contact details.
* Recommend products.

**Education and training:**

* Put subject experts into courses.
* Give interactive tutors for complex topics.
* Give assessments and feedback.

### **Professional Integration**

* **Branding**: Agents match the design of your website.
* **Custom domains**: Agents can run on your own domain.
* **Analytics**: Track conversations and results.
* **Lead capture**: Agents collect user information automatically.

***

## How to Publish to Community

### Step 1: Prepare Your App

Prepare your app for public use before you share it.

**Content review:**

* Remove sensitive data, API keys, and personal information.
* Use general example data that shows the functions.
* Make sure that all text is professional and helpful.
* Test all features.

**Documentation:**

* Add a clear description of what the app does.
* Add setup steps if the app needs integrations.
* Give example use cases and benefits.
* Add a short "how it works" explanation.

### Step 2: Publish to Community

1. Open your Taskade Genesis app in your workspace and publish it. You cannot share a draft.
2. Click **Publish** in the top toolbar.
3. Under **More options**, turn on **Show in public listings**.
4. To let people copy the app, open **Let others clone** and choose **Free** or **Paid**. This also turns on the public listing.
5. Give the app a clear name and description. Taskade puts the listing into a category for you.

After you publish an app that you built, the dialog that says your app is live can show **Share as a free template in the app gallery**. Click **Add** to do the same as **Let others clone** set to **Free**.

### Step 3: Manage Your Community App

**Track performance:**

* See the counts of views, likes, and clones (installs).
* See the intelligence score of your app.
* Track visitors with App Analytics (Business and up).

**Keep the app up to date:**

* Regular updates help people find your app.
* Correct the problems that community users report.
* Add new features from their feedback.

***

## Forking Apps from Community

### What is App Forking?

A fork is a complete, independent copy of a Taskade Genesis app in your workspace. You get the projects, AI agents, automations, media files, and settings. You can use and change all of them.

### Finding Apps to Fork

**Browse the community marketplace:**

* **By category**: business tools, customer service, online stores, and more
* **By popularity**: most forked, highest rated, recently updated
* **By industry**: restaurants, healthcare, consulting, retail, and more
* **By features**: file uploads, payments, and automation complexity

**Search and filter:**

```
Search: "customer feedback restaurant"
Browse: categories such as Dashboards, CRMs, Websites, and Forms
```

### How to Fork an App

1. Find the app that you want at [taskade.com/apps](https://www.taskade.com/apps).
2. Click **Preview** to try the app.
3. Open **Workspace** to see the projects, agents, and automations in the app.
4. Click **Clone**. This button shows only when the creator offers the app as a kit.
5. If you have more than one workspace, choose the destination workspace.
6. Wait 30 to 60 seconds while Taskade copies the app.

Your forked app then shows in your workspace, and it works.

A creator can archive a kit or the workspace behind it. Taskade can also take a kit down. In both cases, the kit page says that the app is no longer available, and it has no **Clone** button. A person who bought a paid kit can still clone it. A copy that you cloned before stays in your workspace.

### What You Get When Forking

**Full copy of the workspace parts:**

* **All projects**: data structures, custom fields, and templates
* **AI agents**: trained agents with their knowledge and personalities
* **Automations**: workflows and triggers. Connect your own third-party accounts, because Taskade does not copy connected accounts and secrets.
* **Media files**: images, documents, logos, and assets
* **Settings**: permissions and customizations

**Independence:**

* Your fork is separate from the original.
* Your changes do not change the source app.
* You can update, rebrand, or change the fork.
* Your fork has no connection to the original creator.

***

## Fork vs. Template vs. Clone

Each approach gives a different result.

**Fork** (a copy of a community app):

* Content: the complete set of workspace parts
* Data: example data included
* Agents: fully trained
* Automations: workflows. Connect your own accounts
* Changes: you can edit everything

**Template** (a Taskade template):

* Content: the structure only
* Data: empty or placeholder data
* Agents: a basic setup
* Automations: a framework only
* Changes: you can change a lot

**Clone** (a copy of your own app):

* Content: an exact copy
* Data: your real data
* Agents: the same training
* Automations: all your integrations
* Changes: the copy starts identical to your app

***

## Best Practices for Community Success

### Creating Shareable Apps

**Design your app for reuse:**

```
❌ "Sarah's Restaurant Feedback System"
✅ "Restaurant Customer Feedback & Manager Alerts"

❌ Hard-coded email addresses and phone numbers
✅ Placeholder values that users can easily customize

❌ Complex setup requiring 10+ integration steps
✅ Simple setup with clear documentation
```

**Include complete examples:**

* Sample data that shows all features
* Example automations that work by default
* Clear names that make sense to other people
* Help text and tooltips that explain the business rules

### Writing Great Descriptions

**Say what value the app gives:**

```
❌ "Helps with customer stuff"
✅ "Collects customer feedback with 1-5 star ratings, instant manager alerts for low scores, and weekly performance reports"

❌ "Good for restaurants"
✅ "Perfect for restaurants, cafes, food trucks, and any food service business wanting to improve customer satisfaction"
```

**Give the setup requirements:**

```
"This app works immediately after forking, but for full functionality you'll need:
• Slack workspace for manager alerts (5 minutes)
• Email service for customer confirmations (optional)
• No coding or technical knowledge required"
```

### Optimizing for Discovery

**Choose good tags:**

* **Business function**: "feedback", "booking", "inventory", "crm"
* **Industry**: "restaurant", "healthcare", "consulting", "retail"
* **Features**: "mobile-friendly", "payments", "automation", "reporting"
* **Skill level**: "beginner", "intermediate", "advanced"

**Update regularly:**

* Correct the bugs that community users report.
* Add requested features.
* Keep screenshots current after UI changes.
* Answer comments and questions.

***

## Popular Community Categories

### Customer Experience

* **Feedback collection**: rating systems and review management
* **Support portals**: ticket systems and knowledge bases
* **Booking systems**: appointments, reservations, and schedules
* **Onboarding flows**: welcome sequences and setup wizards

### Business Operations

* **Inventory management**: stock tracking and reorder alerts
* **Lead management**: sales pipelines and follow-up systems
* **Employee tools**: onboarding and performance tracking
* **Financial tracking**: expense reports and budget tracking

### Content & Marketing

* **Content calendars**: social media plans and publication schedules
* **Campaign tracking**: marketing performance and ROI analysis
* **Brand management**: asset libraries and style guide rules
* **Event management**: registration and attendee tracking

### Industry-Specific Solutions

* **Restaurant**: menu management, table reservations, and staff schedules
* **Healthcare**: patient intake, appointment reminders, and billing
* **Real estate**: property listings, client management, and tour schedules
* **Education**: course management, student tracking, and assignment submission

***

## Privacy & Security Considerations

### Before Publishing

**Clean the data:**

* Remove all real customer data, and put in examples.
* Remove API keys, passwords, and credentials.
* Remove email addresses, phone numbers, and personal information.
* Read all text fields for sensitive business information.

**Examine access control:**

* Make sure that no private integrations stay connected.
* Remove workspace-specific permissions.
* Clear personal settings and preferences.
* Test with a new account to make sure that the app is clean.

### Community Guidelines

**Prohibited content:**

* Apps that contain real personal or business data
* Malicious code or security exploits
* Content or branding that breaks copyright
* Spam or low-quality submissions

**Best practices:**

* Use placeholder data that shows the functions clearly.
* Give credit for third-party resources.
* Respect intellectual property, and make original solutions.
* Give honest and correct descriptions of what the app does.

***

## Analytics & Performance

### Community App Metrics

**Core statistics:**

* **Install count**: how many users cloned your app
* **View count**: total views of your listing
* **Like count**: how many people liked your app
* **Intelligence score**: how complete the Workspace DNA of your app is

**Performance insights:**

* **App Analytics** (Business and up): visitors, pageviews, top pages, referrers, devices, and locations
* **User feedback**: common questions and requests
* **Update impact**: how your changes affect usage

### Growing Your Community Presence

**Engagement:**

* **Answer questions**: help the people who clone your app.
* **Update regularly**: add new features to your apps.
* **Cross-promotion**: mention your apps in forum discussions.
* **Documentation**: write helpful guides and tutorials.

**Reputation:**

* **Quality over quantity**: build finished, useful apps.
* **User support**: help community members use your apps.
* **New ideas**: build new kinds of solutions.
* **Collaboration**: work with other community builders.

***

## Advanced Community Features

### Embedding Community Apps

A published community app is a standard Taskade Genesis app. You can put it in a web page with an `<iframe>` that points at its published address:

```html
<!-- Embed a published community app -->
<iframe src="https://your-app.taskade.app"
        width="100%"
        height="600"
        frameborder="0">
</iframe>
```

Copy the exact snippet with **Copy Embed Code** in the **Publish** panel of the app.

### API Integration with Community Apps

An app that you clone from the community is a standard Taskade Genesis app. Build integrations with the [public API](https://docs.taskade.com/developers/developer-home.md). An app can call external services securely through the [App Secrets](https://docs.taskade.com/taskade-genesis/space-apps-guide/app-secrets.md) outbound proxy. There is no separate `community` API surface.

### Collaborative Development

**Community feedback:**

* Feature request votes
* Bug report tracking
* Shared improvement ideas
* Documentation that the community writes

***

## Troubleshooting Common Issues

### Publishing Problems

**Problem**: The app does not publish to the community. **Solutions**:

* Remove all sensitive data.
* Make sure that the app is published, not a draft.
* Ask the workspace owner to share the app as a kit. Only the workspace owner can do this.
* Read the content guidelines and obey them.

**Problem**: Few people find or fork the app. **Solutions**:

* Give specific benefits in the app description.
* Add better screenshots and preview content.
* Choose better tags and categories.
* Answer user reviews and questions.

### Forking Problems

**Problem**: The forked app does not work correctly. **Solutions**:

* Find out if the original app needs specific integrations.
* Read the setup steps from the creator.
* Make sure that all media files arrived.
* Contact the app creator for help.

**Problem**: You cannot change the forked app. **Solutions**:

* Make sure that you own the forked copy.
* Examine the workspace permissions and roles.
* Make sure that you edit the fork, not the original.
* If the limits look wrong, contact Taskade support.

***

## Resources & Support

### Community Documentation

* [**Community Guidelines**](https://www.taskade.com/learn/genesis/community-gallery): rules and best practices
* [**Publishing Checklist**](https://www.taskade.com/learn/genesis/publishing): review steps before you publish
* [**Community Success Tips**](https://www.taskade.com/learn/genesis/community-kits): grow your presence

### Getting Help

* **Community forum**: talk with other builders and users.
* **Creator support**: a support channel for active community creators.
* **Documentation requests**: help improve the community resources.
* **Bug reports**: report problems with community features.

### Learning Resources

* **Community showcase**: featured apps and case studies
* **Builder interviews**: lessons from successful community creators
* **Best practice guides**: detailed tutorials and examples
* **Video walkthroughs**: step-by-step build and publish guides

***

## Ready to Share Your Genius?

Share your feedback system, inventory tracker, or team dashboard with the Taskade community. Your app helps other teams, and it shows your skills.

### Quick Start Checklist

* [ ] **Review your app**: remove sensitive data and finish the app.
* [ ] **Test all features**: use example data.
* [ ] **Write a clear description**: give the value and the use cases.
* [ ] **Add screenshots**: show preview content.
* [ ] **Choose good tags**: help people find the app.
* [ ] **Publish to the community**: read the first feedback.
* [ ] **Talk with users**: answer the people who fork and review your app.

### Next Steps

1. Browse Taskade App Factory for ideas, and see which App Kits are popular.
2. Fork a few apps to learn the user experience.
3. Find gaps in the marketplace where your knowledge can help.
4. Build your solution, and plan to share it.
5. Publish your first app to Taskade App Factory.

***

**🌟 Build an app. Share it. Help other teams work better.**

***

*Step-by-step guides on taskade.com/learn:* [*Publish and Clone Your Apps*](https://www.taskade.com/learn/genesis/publishing)*,* [*Builder Community & App Kits*](https://www.taskade.com/learn/genesis/community-kits)*,* [*Browse & Clone Community Apps*](https://www.taskade.com/learn/genesis/community-gallery)*.*
