Team Collaboration & Private Homepages
Private vs. public
When you publish a workflow on Floyo, it goes to the public community library. Anyone can find and run it. That's great for sharing with the world. It's not what you want for client work, proprietary processes, or anything your team considers internal.
Private homepages and team workflows solve this. They let you share workflows within your team without making them public.
Your team's private homepage
Every team has a private homepage. It's the first thing team members see when they switch to the team workspace. Think of it as the team's internal dashboard.
To access it:
- Click your profile icon (top right)
- Select Private Homepage from the dropdown
From here you can browse all workflows that have been shared to the team.
Adding workflows to your private team
You don't need to publish a workflow to share it with your team. Upload the JSON directly to your team's private homepage:
- Go to your team's private homepage
- Click the upload option
- Select a workflow JSON exported from ComfyUI
- Add a name, preview image, and description
The workflow appears as a card on the private homepage. Team members can click it and run it in the Floyo canvas. It never touches the public library.
Write clear descriptions and use consistent tags across your team's workflows. When you have 50+ workflows, good naming and tagging is the difference between finding what you need in seconds and scrolling for minutes.
Team pages vs. private homepage
| Private homepage | Team pages (Lesson 1) |
|---|---|---|
Purpose | Quick access to shared workflows | Organized playbooks with documentation |
Content | Workflow cards only | Headers, text, galleries, workflow cards, HTML |
Created by | Anyone uploading a workflow | Owners and admins using the page editor |
Best for | "Here's a workflow, use it" | "Here's how our team works" |
Use both. The private homepage for quick sharing. Team pages for structured documentation.
Working together in practice
A typical team workflow looks like this:
- Someone builds a new workflow in the canvas
- They test it, get good results, and export the JSON
- They upload it to the private homepage with a clear name and description
- If it becomes a standard part of the team's process, an admin adds it to the production playbook (a team page from Production PlaybookLesson 1)
- Run history (Run HistoryLesson 2) tracks every time anyone runs it and what results they got
Floyo workflows are tied to the team's model library. If the workflow uses a custom LoRA (Uploading Custom Models & LoRAsLesson 3), every team member already has access to it. No file syncing needed.
FAQ
Can external collaborators access private team content?
Only invited team members can access private homepages and team pages. For external collaborators, invite them to the team with the member role, or use password-protected team pages.
What happens to shared workflows if a team member leaves?
Workflows uploaded to the team stay with the team. The person's personal workflows stay with their account. Nothing is lost.
Can I move a private workflow to the public library later?
Yes. You can publish any workflow to the community library at any time. Going public doesn't remove it from your private team.