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
workspaceIdare the recommended and future-proof option. - SDK setups using
environmentIdare 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.
Recommended Migration
1
Open Connect Your App
In Formbricks, go to Settings → Workspace → 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
FAQ
Do I Need To Rotate IDs Immediately?
No. Legacy setups continue to work during the migration period. However, new implementations should always useworkspaceId.