Improved
Scope Custom Experiences to a Workspace
August 6th, 2026
You can now scope a Custom Experience to a single Workspace instead of the entire Organization.
Set the new workspace_id field when you create or update a Custom Experience:
- Leave
workspace_idempty to keep the Custom Experience scoped to your Organization. This is the default, so your existing Custom Experiences are not affected. - Set
workspace_idto a Workspace ID to scope the Custom Experience to that Workspace.
workspace_id is also returned when you list, create, retrieve, or update a Custom Experience.
A workspace-scoped Custom Experience can only be applied to a resource in the same Workspace: a Signature Request, a Template, or a Workflow Template. An organization-scoped Custom Experience can still be applied to any resource.
With a workspace-scoped API key, you can view and manage organization-scoped Custom Experiences plus the workspace-scoped ones in your authorized Workspaces. An organization-scoped API key can view and manage every Custom Experience.