Connected

Configuration

Set up org-level controls first, then turn on policy guards such as API access and suppressions.

Use this order to keep operational changes low-risk.

1) Workspace settings

Set workspace defaults (name, from address, timezone, webhook URL) before creating automation workflows.

2) API keys

Create/revoke API keys for MCP tooling, automation, and server integrations.

3) Suppression policy

Protect deliverability by blocking bounce/complaint and unsubscribe recipients.

4) Opencode setup

5) Daily operations

Keep routing and safety settings in sync with UI validation and MCP checks.

Use this sequence when enabling configuration features.

01Start with Workspace and API access to define org-level behavior.
02Then configure suppressions only after route and domain health are stable.
03Set up Opencode config and local hooks so your ChatGPT/Codex layer works with organization context.
04Use Deliverability checks to confirm suppression-driven bounce reduction.
05Review these settings periodically after major domain or key rotations.