Skip to main content
This is a Flox for Teams featureThis is a paid feature included with Flox for Teams.
An organization in FloxHub represents a shared workspace for teams. It provides:
  • A private catalog
  • Scoped access control
  • A foundation for collaboration among multiple users
This document outlines how organizations work today, and how they can be managed.

​
User Membership

A user can belong to more than one organization. This allows users to use a single FloxHub account in multiple contexts.

​
Permissions and Access Control

Organizations in FloxHub use role-based access control (RBAC) to assign permissions to organization members. A user can have one of the following roles within an organization:
  • Owner: Full administrative access, including managing members and settings.
  • Writer: Can create and update environments and packages, but cannot manage members or organization settings.
  • Reader: Can view and pull environments and can install packages, but cannot create or modify them.
The organization must have at least one owner, but may have multiple. Owners can manage the organization, including adding or removing members and changing roles. Owners may not modify their own role or remove themselves from the organization.

​
Enterprise SSO

Organizations can connect their own identity provider, so members sign in with their work accounts and join the organization automatically on first sign-in. Owners set the connection up themselves from the organization’s settings page. See Enterprise SSO for how sign-in works and how to set it up.

​
Service Accounts

A service account is an identity your automation signs in with, such as a release pipeline or a nightly test run. It belongs to the organization rather than to the person who created it, has read-only or read and write access across the organization, and authenticates with its own tokens. Only owners can create service accounts and issue their tokens. See Service accounts for how to set one up and how to rotate its tokens.

​
Environment Visibility and Management

Organizations in FloxHub include a view of all environments and packages owned by the organization. For each environment, users can:
  • See the live generation and a history of changes
  • Configure basic settings, such as owner and name
  • Delete environments
For each package, users can:
  • See package details, including supported systems and available versions
Environments and packages created within an organization are visible to all its members, with access governed by the organization’s RBAC configuration.