Workspace Defaults save integration configuration, not API keys. When creating the workspace, expand the default settings list, enter the required key, and verify it. If you skip this step, the integration stays pending until you add the key.
Configure Workspace Defaults
Workspace Defaults let you configure a reusable setup once and apply it when creating new workspaces. Use them to keep client and team workspaces consistent without rebuilding labels, exclusions, Reply Agents, workflows, and other settings each time.
Set Up Workspace Defaults
Open Settings → Workspace Defaults.
Choose the settings you want to reuse in new workspaces.
Configure and save each relevant category.
Review the saved configuration before creating a new workspace.
Settings You Can Reuse
Labels
Create the labels that should appear in new workspaces, such as Positive, Negative, and Neutral. These labels were confirmed to import successfully during QA.
Exclusions
Use Import from Current Workspace to bring existing exclusions into your defaults. Remove entries you do not want, then save. QA confirmed that configured exclusions, including blocked domains and custom codes, imported into a new workspace.
Reply Agents
Save a default Reply Agent and its configuration. In QA, an agent configured with Human in the Loop, Professional tone, and OpenAI provider was imported successfully. The agent still needs working channels and the required provider credentials before you can test real replies.
Workflows
Import workflows from an existing workspace and include them in the default configuration. QA confirmed that five imported workflows appeared in the new workspace and were active. After creation, review each workflow's trigger, actions, and external dependencies before relying on it.
Workspace Limits
Configure the available limits for new workspaces. QA confirmed that limits set to unlimited were applied correctly. Review the limits after creation to make sure they match the workspace's intended use.
Integrations
Choose the integrations you want included in the default configuration. For security, API keys are not stored in Workspace Defaults. You can provide and verify the keys while creating the new workspace. If you skip a key, the integration remains pending and can be connected later.
AI Labeling
Configure AI Labeling defaults, including the Relabel old replies option where applicable. As with integrations, the configuration is saved but the API key is not stored in Workspace Defaults. Provide and verify the key when creating the workspace, or complete setup afterward.
Webhooks
Webhook settings are supported in Workspace Defaults. After creating a workspace, review the configured webhook destinations and test delivery. Webhook imports were not covered in the available QA report.
Apply Default Settings When Creating a Workspace
Go to Settings → Workspaces → Add Workspace.
Enter the workspace name, description, timezone, and limits.
Enable Apply default settings to the workspace.
Expand the default settings list to review the configuration being applied.
For integrations and AI Labeling that require credentials, enter the API key in the corresponding row and verify it. The HeyReach key field is shown only when HeyReach is enabled on your plan.
Create the workspace.
Open the new workspace and verify the imported settings and connection statuses.
Integration credentials do not carry over from Workspace Defaults. If you skip a required key during workspace creation, the item stays pending with an Add key option. You can complete setup later from the relevant Integrations or AI Labeling page.
Check Your New Workspace
Labels: Confirm that all selected labels are present.
Exclusions: Confirm that the intended blocked domains and other exclusions were imported.
Reply Agent: Review its settings and connect the channels and credentials needed to test replies.
Workflows: Confirm the expected workflows exist and are active; test any external notification actions.
Workspace Limits: Confirm the configured limits.
Integrations and AI Labeling: Check whether each item is connected or pending and complete any missing verification.
Webhooks: Review destinations and send a test event.
Workspace Defaults vs. Cloning
Workspace Defaults provide a reusable configuration that you apply when creating a new workspace. Cloning copies selected settings from a particular existing workspace. Neither process should be treated as a substitute for checking new workspace connections and permissions.
For workspace creation and cloning instructions, see How to Add a Workspace.
Frequently Asked Questions
Why did an integration show as connected in my defaults but not in the new workspace?
Can I add integration credentials after creating the workspace?
Yes. A skipped item remains pending with an Add key option. You can complete its setup later from Integrations or AI Labeling.
Does the Reply Agent start sending immediately?
Not necessarily. An imported Reply Agent still requires working channels and any necessary provider credentials before live replies can be tested.
What if an imported workflow is not working?
Check that it is active, then review its trigger, conditions, and actions. Verify external integrations and notification destinations used by the workflow.