General
Configure workspace profile (name, timezone) and default LLM model selection. These settings cascade to workflows and agents that use default placeholders.
Secrets
Manage encrypted provider credentials required for integrations like the Claude Agent SDK.
General Settings
The General tab (Workspace → Settings → General) contains three configuration fields that define your workspace identity and defaults. All fields are saved together when you click Save Changes.
Open the workspace
From the global workspace switcher, choose the workspace you want to configure.
Navigate to Settings → General
Click Settings in the left rail and stay on the General tab. The current workspace settings are displayed.
Update settings
Modify any of the three fields: workspace name, timezone, or default LLM model. See the sections below for details on each field.
Save changes
Click Save Changes. A confirmation message appears when your changes are saved successfully.
Workspace Name
The workspace name identifies your workspace throughout the application. It appears in workspace switchers, breadcrumbs, and other UI elements.- Required: Yes
Timezone
The timezone selector determines when scheduled workflows execute. The field displays a curated list of major world timezones, sorted by UTC offset and showing current offset information (e.g., “(UTC-8) America Los Angeles (PST)”).- Default: UTC
- Description: Timezone used for scheduled workflows. All workflows will run according to this timezone.
Default LLM Model
The Default LLM Model selector sets the workspace-wide default that workflows and agents inherit when they use the default model placeholder. This value is resolved at runtime through a cascading priority system.- Default: Falls back to system default if not set
- Description: Default model used by agents in this workspace when no other model is specified
Teams should leave workflow and agent model pickers at their default model placeholder unless they have a justified override. Once the workspace value is set, all placeholder usages resolve to the workspace default without per-workflow setup.
How existing vs. new workflows behave
- Existing workflows keep running exactly as configured. Any step that already has a specific model selected continues to use it. Steps that use the default model placeholder immediately inherit the newly saved workspace value during the next execution.
- New workflows (and newly created agents) start with the default model placeholder. Until you set a workspace default, those executions fall back to the platform-wide system default. After you set it once, every new workflow automatically inherits it.
- No retroactive edits occur—this feature relies on runtime resolution, not bulk edits to workflow definitions. You can therefore experiment safely without rewriting historical definitions.
Model resolution order
When a workflow step runs, the system determines which model to use by checking the following sources in priority order:| Priority | Source | When it wins |
|---|---|---|
| 1 | Coordinator override | A coordinator or runtime hook explicitly overrides (e.g., manual re-run forcing a model). |
| 2 | Agent/step config | The agent definition itself has a specific model selected (Agent Builder, Agent Run/Session forms). |
| 3 | Workflow default | The workflow metadata form has a default model set. See the Workflow Metadata defaults guide for workflow-level overrides. |
| 4 | Workspace default | The value saved on the General tab; applies whenever upstream layers use the default model placeholder. |
| 5 | System default | The platform-wide fallback when every other layer uses the default placeholder. |
Secrets Management
The Secrets tab (Workspace → Settings → Secrets) manages encrypted provider credentials required for integrations. The Claude API key is specifically required to use the Claude Agent SDK as an execution engine in your workflows.
Open Settings → Secrets
Click Settings in the left rail and navigate to the Secrets tab. The current Claude API key status is displayed.
Set or update the key
Enter a new Claude API key (the field is never pre-filled for security) and click Set Key or Update Key. The form clears once the key is saved successfully. If a key already exists, you’ll see a confirmation message: ”✓ API key is currently configured.”
Clear when needed
Use Clear Key to remove the stored secret. A confirmation dialog guards against accidental removal.
Secrets are encrypted at rest and never exposed to the browser. The form field is always empty for security reasons, even when a key is already configured. A confirmation message indicates whether a key exists without revealing its value.
Related references
- Claude Agent SDK Integration — learn how to use Claude as an execution engine in your workflows.
- Workflow Metadata defaults — covers per-workflow model overrides.
- Agent builder — describes per-agent model choices and when to use the default model.