01
Multi-workspace organization
Create separate workspaces for different teams, departments, or clients. Each workspace has its own boards, members, and settings. Switch between workspaces instantly.
// Workspaces & Teams
The right access for every role.
Organize boards into workspaces with four-tier role-based access control. Viewers read. Members build. Admins manage. Owners control. Every API key is workspace-scoped with granular permissions.
02
Four-tier role-based access
Owner, admin, member, and viewer roles with clear permission boundaries. Viewers can read everything but cannot create or modify. Members handle day-to-day work. Admins manage members and settings. Owners control the workspace.
03
Invitation system
Invite team members by email with a specific role. Invitations are workspace-scoped - joining one workspace does not grant access to others.
04
Workspace-scoped API keys
Issue API keys that are scoped to a specific workspace with read or write permissions. Integrations and AI agents get exactly the access they need and nothing more.
05
Per-board member visibility
Board API responses include the member list with names, initials, and avatar URLs. Assignee pickers show only workspace members - no global user search, no data leakage.
06
Workspace settings and customization
Admins configure workspace name, default board settings, and member roles from a single settings page. Board-level settings (backgrounds, done columns, card prefixes) are independent per board.
01 What roles are available?
+
Flux has four roles: viewer (read-only), member (full CRUD on boards, cards, columns, labels, attachments, comments, and checklists), admin (member permissions plus workspace settings, member management, and invitations), and owner (all admin permissions plus workspace deletion).
02 Can someone be in multiple workspaces?
+
Yes. A user can belong to any number of workspaces, each with a different role. Switching workspaces is instant and preserves your current board state.
03 How do invitations work?
+
Admins and owners can invite users by email with a specific role. The invitee receives an email link, signs up or logs in, and joins the workspace with the assigned role.
04 Can I restrict API key access to one workspace?
+
Yes. API keys are workspace-scoped by default. When creating a key, you select the workspace and the permission scope (read, write). The key cannot access boards in other workspaces.
// Build your team
Create a workspace. Invite your team.
Free to start. Roles and permissions work out of the box.