Skip to main content
A workspace is an isolated environment containing all your Fileloom resources. Each workspace has its own templates, files, API keys, team members, and billing.
Workspaces

Switching Workspaces

Use the workspace dropdown at the top of the sidebar to switch between workspaces. The dropdown shows:
  • Workspace name
  • Your role (Owner, Editor, Viewer)
  • Settings icon for quick access

Creating a Workspace

1

Open Workspace Menu

Click the workspace dropdown in the sidebar.
2

Click Create Workspace

Select “Create New Workspace” from the menu.
3

Enter Details

Provide a name for your workspace. A URL-friendly slug is generated automatically.
4

Confirm

Click “Create” to set up your new workspace.
New workspaces start on the Free plan. Upgrade anytime from the Billing section.

Workspace Settings

Access workspace settings by clicking the gear icon next to your workspace name.

General Settings

SettingDescription
NameDisplay name for the workspace
SlugURL-friendly identifier
Storage ModeWhere to store generated PDFs

Storage Modes

Configure how Fileloom stores your generated PDFs:
ModeBehavior
FileloomStore in Fileloom storage only (default)
ExternalStore in your AWS S3 or Supabase only
BothStore copies in both locations
See Integrations for external storage setup.

Workspace Roles

Team members can have different access levels:
RolePermissions
OwnerFull access, billing management, can delete workspace
EditorCreate/edit templates, manage files, view API keys
ViewerRead-only access to templates and files

Workspace Limits

Resources are limited per workspace based on your plan:
ResourceFreeStarterGrowthScale
Team Members23510
Templates550UnlimitedUnlimited
API Keys12510
Retention7 days30 days90 days180 days

Deleting a Workspace

Deleting a workspace permanently removes all templates, files, and API keys. This action cannot be undone.
Only workspace owners can delete a workspace:
  1. Go to Workspace SettingsGeneral
  2. Scroll to the danger zone
  3. Click Delete Workspace
  4. Confirm by typing the workspace name

Best Practices

  • Separate environments — Create workspaces for development, staging, and production
  • Client isolation — Use separate workspaces for different clients or projects
  • Team organization — Group related projects in a single workspace for shared access