Skip to main content
Every API key belongs to one workspace. When your workspace is a partner workspace, its keys also manage the workspaces you created for your clients: they create workspaces, list them, and act inside a managed workspace by naming it with the Plane-Workspace header. Requests to a workspace your partner does not manage are rejected.

​
Workspace defaults

Plane can configure defaults for the workspaces your partner creates. Defaults apply during workspace creation, before the API returns, so your integration can use the configured features immediately. The partner’s defaults configuration has two sections:
Feature defaults use enabled: true or enabled: false for toggleable features. Preferences use registered workspace preference keys and their supported values. Omitted entries keep Plane’s normal defaults. If a configured default cannot be applied, workspace creation fails without leaving a partially configured workspace. Changing defaults affects future workspaces only. Existing workspaces keep their configuration. Defaults do not approve the workspace, verify its entity, or activate payment or payroll capabilities. Contact Plane to configure your partner’s defaults; they are not writable through the public API.

​
Webhooks

Events in a managed workspace are delivered to that workspace’s webhook endpoints and to your partner workspace’s endpoints. Configure endpoints once in your partner workspace and use each event’s workspace field to tell which managed workspace it came from. Each message is also tagged with the source workspace ID as a channel, so an endpoint can filter to one managed workspace.