Skip to main content

Documentation Index

Fetch the complete documentation index at: https://formbricks.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Formbricks deprecated the legacy Environment ID for SDK setup and now uses Workspace ID as the primary identifier.
Existing SDK integrations that still use environmentId continue to work for now. New and updated integrations should use workspaceId.

​
Why This Changed

Formbricks moved from an environment-centric model to a workspace-centric model to simplify setup, reduce confusion, and align product terminology across the app, SDKs, and API surfaces.

​
Terms To Know

  • Workspace ID: The canonical identifier for SDK setup and current product workflows.
  • Environment ID (legacy): A backward-compatible identifier that may still appear in older integrations.

​
What Still Works

  • SDK setups using workspaceId are the recommended and future-proof option.
  • SDK setups using environmentId are still accepted during the migration period.
  • If your app is already connected and sending data with a legacy Environment ID, no immediate outage is expected.
1

Open Connect Your App

In Formbricks, go to Settings → Connect Your App.
2

Copy Your Workspace ID

Use the Workspace ID field as the canonical ID for all new SDK setup changes.
3

Update SDK Initialization

Replace legacy environmentId config usage with workspaceId in your integration snippets.
4

Keep appUrl Unchanged

Keep your existing appUrl value unless your hosting/domain setup changed.

​
SDK Example

import formbricks from "@formbricks/js";

formbricks.setup({
  workspaceId: "<your-workspace-id>",
  appUrl: "<your-app-url>",
});

​
FAQ

​
Do I Need To Rotate IDs Immediately?

No. Legacy setups continue to work during the migration period. However, new implementations should always use workspaceId.

​
Do Test And Production Workflows Change?

No. Your development/testing and production workflows remain the same. This migration only changes the canonical identifier you should use in SDK setup.

​
Where Can I Find Detailed Setup Guides?

Use the Framework Guides for framework-specific SDK instructions.