---
title: Production Playbook
slug: production-playbook
createdAt: 2026-06-15T09:30:28.642Z
---

# Building a Production Playbook for Your Team



::embed[]{url="https://youtu.be/onK7llKAQXI?si=V6avPMlUp5RbMioi"}



## The problem

Most teams share ComfyUI workflows by exporting JSON and dropping it in Slack, Google Drive, or a shared folder. That works for a while. Then someone runs an old version. Someone else can't find the workflow they need. The model files don't match. Nobody knows which workflow produced last week's deliverable.

A production playbook solves this. It's a single page where your team finds the workflows they need, the documentation that explains them, and the examples that show what good output looks like.

## What a team page is

A team page on Floyo is a private landing page visible only to your team members. Think of it as an internal homepage. You build it with blocks: headers, rich text, workflow cards, image galleries, and custom HTML.

Workflow cards are the key. They're not links to JSON files. They're live, runnable workflows. A team member clicks one and it opens in the Floyo canvas, ready to run.

## Creating your first playbook

1. Open your team home from the top navigation
2. Go to the **Pages** tab and click the **+** card
3. The page editor opens with a blank canvas



:::hint{type="success"}
Start simple. One header, a short description of what your team produces, and 3-5 of your most-used workflows. You can always add more later.
:::

## Adding workflows

Drag a **Workflow block** into the canvas. Select the workflows you want to include. Each one appears as a card with a preview image, title, and description. Team members can run any of them directly from the page.

Good playbook organization:

- Group by use case (product photos, social content, video generation)
- Or group by pipeline stage (input prep, generation, upscaling, post-processing)
- Add a header block above each group

## Adding documentation

Use **Rich Text blocks** for process notes, style guidelines, or model requirements. Use **Gallery blocks** to show reference outputs so the team knows what quality standard to hit.

## Publishing

Click **Preview** to check the layout, then **Publish**. The page is now visible to all team members. Only team members. It's not public.



:::hint{type="warning"}
You can password-protect a page for an extra layer of access control. Useful if your team has contractors or external collaborators.
:::



## FAQ

**Can I update the playbook after publishing?**

Yes. Edits save automatically. Published pages are always showing the latest version.

**Who can create team pages?**

Owners and admins. Regular members can view and run workflows from team pages but can't create or edit them.

**Is there a limit on how many workflows I can add?**

No. Add as many as you need. For large teams, consider splitting into multiple pages by department or project.