COMMUNITY PAGE
Floyo Enterprise: 6 Walkthroughs to Share With Your Team
The fastest way to get your team up to speed on the platform is to show them. Below are 6 short videos covering the enterprise features that come up most often in production. Share them with your team, drop them into an internal kickoff, or watch them yourself to dig deeper. Each one is short.
TL;DR
Who should watch what:
- Producers and creative leads: sections 1 and 2 (team collaboration, building pipeline pages)
- Artists and operators: sections 1, 3, and 4 (day-to-day work)
- Admins, finance, IT: sections 5 and 6 (governance, usage, access, model and node controls)
New to the platform? The enterprise walkthrough covers how Floyo works day to day, feature by feature. Floyo 101 for enterprise and teams →
1. How Teams Collaborate on Floyo
Every team gets a private homepage where all your production workflows live. Same nodes, same models, same settings, for everyone, every time. When someone updates a workflow, the update is live for the team instantly.
This is the layer that makes shared production possible: no JSON files passed around, no version drift, no missing dependencies.
"Every team has a private team homepage where you can curate all the workflows needed for your production pipeline, along with examples and notes for your teammates. All workflows are instantly runnable by anyone on the team."
Every workflow lives behind a single runnable link. Send it to a teammate, they hit Run, and it executes with the same models and nodes every time. No JSON exports, no environment debugging, and new hires run their first workflow in minutes.
How Private Workflow Sharing Works ➜
2. Building Your Team's Production Playbook with Private Team Homepages
Private team pages are where workflows get organized and documented. Hero images, chapter headers, descriptions, markdown notes for context and tips, and embedded workflows your artists can run with one click. Add community workflows or your team's own.
Password protect pages when you're working with clients or sensitive projects.
This is where you turn workflow chaos into a production playbook your artists actually use.
"Your homepage is the default space where all the private workflows your team has created populate. Pages let you organize those workflows into docs with sections, pro tips, and more."
Ready to build your own playbook?
Create a Team Page ➜
3. Run History: Reproducibility on Every Generation
Every workflow run is logged with exact settings, inputs, and outputs. Open any run, your own or a teammate's, in a new tab. Tweak one value. Rerun. Open as many runs at once as you want.
Perfect reproducibility, no screenshots, no guesswork. Run History is included on individual, teams, and enterprise plans.
"Every workflow run is accessible in run history. Click any run to open it in a new tab. Settings and values are identical to what you and your teammates have run in the past. Tweak as much as you like and rerun without any guesswork."
Every run is stored with its full state: each node, setting, model, input, and output, including failed runs. Reopen any past run, change a single value, and keep going. Retained for the life of your account.
How Run History Works ➜
4. Upload Your Own Models to a Shared File System
Drop your custom LoRAs, fine-tunes, and checkpoints into your team's unified file system once. They show up immediately in any Load LoRA node and are available to anyone with access.
Your IP stays private. Your team works from the same shared assets, automatically. No more "can you send me that LoRA?" Slack pings.
"Click the My Files icon on the sidebar, navigate to the appropriate subfolder, upload your file, and it shows up in your files and in your Load LoRA node."
Upload once and your custom LoRAs, fine-tunes, and checkpoints are available to only those in your team with access, ready to select in any Load LoRA node.
How to Upload LoRAs and Models ➜
5. Team Admin and Account Management
The admin side. From the profile menu or teams switcher, admins can create teams, assign unique team URLs, manage member roles, see pending invites, and adjust plans and balances.
Usage breaks into three buckets, all in one place:
FloTime consumed when you hit generate
Floyo Partner Nodes for closed-source AI model costs, so nobody on your team has to manage third-party API keys or separate accounts
API usage if you're hitting Floyo from an app, site, or plugin you've built
Filter usage by team member, role, or date range. Each individual generation in Run History is labeled with its FloTime, partner node, and API cost.
When you need to silo projects, clients, or teams, spin up additional workspaces with their own plans, members, balances, and storage.
"From your profile menu or teams switcher, click settings. Only admins see this option. Create a team name, assign a team URL, manage members and roles, see who hasn't accepted invites, and adjust roles and access."
Three roles keep access clean: Owner (full control including billing and ownership transfer), Admin (settings, members, models, billing), Member (run workflows and open team files, no settings changes or invites).
Full Permissions Table ➜
Any workflow is, and can also run, as a callable endpoint.
Floyo API Introduction ➜
6. How to Govern Models & Nodes for Your Team
Set the policy for which models and nodes are allowed to run in your workspace. Auto-block any model that isn't Verified Private (a contract prohibits the provider from training on your content) or isn't licensed for commercial use. Check every model's status at trust.floyo.ai.
Block individual models, entire provider families, or any node, including custom, community, and GitHub-sourced nodes.
Every block applies to every run, UI or API, with no execution path that bypasses it. Set governance once at the workspace level and it's enforced uniformly across all traffic, including headless API deployments.
"Auto-block any model that isn't Verified Private or licensed for commercial use, block individual models or entire provider families manually, and deny any node from executing across your workspace."
Every model is reviewed and tagged for Verified Private and commercial-use status. Browse the full list before you set your policy.
Floyo Trust Center ➜
Set model and node policy per team, enforced at the workspace level across UI and API.
Manage Models and Nodes ➜
Next steps
Share this page with anyone on your team who needs to see how Floyo works.
To get hands-on, browse production workflows and run a few in your account.
Build your first production pipeline this week.
Browse production-ready workflows or talk to the Floyo team about a custom enterprise setup.
Matt Shih
CoFounder and Creative Director at Floyo
20+ years of creative experience in advertising and production. Has designed AI production pipelines for animated shorts, commercial campaigns, and studio teams shipping work for major film and advertising clients.
Related Reading
Production Guide: ComfyUI in Production for Studios → Full guide: Licensing and IP for Commercial Production → ComfyUI for Teams: How Studios Share Workflows, Track Results, and Run Production → The Human Touch: Directing AI in Production → Discover Film & Animation workflows → Character Character and Concept Design workflows →Last updated: July 26, 2026