Unsendbox logo
Get started
← RETURN TO ROOT
Connected

Workspace and API access

Control who can operate your org and how automation credentials are managed.

Back to configuration

Workspace settings scope

These settings are org-scoped and apply to all connected team workflows.

workspaceName
Display name used for the organization context.
defaultFromAddress
Fallback sender address suggestion for outbound messages.
timezone
Timezone for scheduling and any time-based operations.
webhookUrl
Optional webhook endpoint for external event integrations.

API key lifecycle

Use API keys for programmatic access and MCP integrations.

  1. 01Open Dashboard → Settings to create keys and copy the raw key immediately (it is shown only once).
  2. 02Store keys in your secret manager and set short-scoped usage with rotation policy.
  3. 03Use key `prefix` to identify active credentials in logs and audit lists.
  4. 04Revoke keys by deleting them from Settings when ownership changes or on rotation.
  5. 05A key’s raw secret is never shown again after creation.

Important behavior

Implementation notes that affect operations.

Org-scoped
Keys are issued per organization and bound to that workspace context for API and MCP flows.
Permission model
Keep access separate by team/process; avoid sharing one key across unrelated workloads.
Deletion impact
Deleting a key removes both org API-key record and MCP auth sync state (no recovery possible).

UI + MCP mapping

Where to operate each action.

  1. 01UI path: `/dashboard/settings` to update workspace settings and manage keys.
  2. 02API surface: settings routes under `/api/v1/organizations/{organizationId}/settings` and `/api-keys` endpoints.
  3. 03Use MCP for chat-driven onboarding and then validate changes in UI before high-volume sending.