Overview
Hub are the building blocks of FLO — they are integrations and connectors (like Google Sheets, Slack, OpenAI, etc.) that users can use in their automation flows. As a platform administrator, you have full control over which hubs are available to your users. This allows you to:- Enforce security policies by restricting access to certain integrations
- Simplify the user experience by showing only relevant hubs for your use case
- Deploy custom/private hubs that are specific to your organization
| Level | Who Can Manage | Scope |
|---|---|---|
| Platform Level | Platform Admin | Install and remove across the entire platform |
| Project Level | Project Admin | Show/hide specific hubs for specfic project |
Platform-Level Management
Platform administrators can manage hubs for the entire FLO instance from Platform Admin → Setup → Hub.Project-Level Management
Project administrators can further restrict which hubs are available within their specific project. This is useful when different teams or projects need access to different integrations.Show/Hide Hub in a Project
1
Open Project Settings
Navigate to your project and go to Settings → Hub.
2
Configure Visibility
You’ll see a list of all hubs installed on the platform. Toggle the visibility for each hub:
- Enabled: Users in this project can use the hub
- Disabled: The hub is hidden from users in this project
3
Save Changes
Changes take effect immediately — users will only see the enabled hubs when building their flows.
Project-level settings can only hide hubs that are installed at the platform level. You cannot add hubs at the project level that aren’t already installed on the platform.
Install Private Hub
If you’ve built a custom hub for your organization, you can upload it directly as a tarball (.tgz) file.
1
Build Your Hub
Build your hub using the FLO CLI:This generates a tarball in
dist/packages/hubs/your-hub-name.2
Navigate to Hub Settings
Go to Platform Admin → Setup → Hub and click Install Hub.
3
Select File Upload
Choose Upload File as the installation source.
4
Upload the Tarball
Select the
.tgz file from your build output and upload it.