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 playbook docid\ l2wi6x8xeidscaxwysao9 ) run history ( run history docid c77gj8vogngkuwoekhav ) 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 & loras docid 9p2n0mdlt2ag satccf47 ), 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