Documentation version: 2026-09-18.3
Canonical: https://docs.creator.gg/guides/readiness.md

# Workspace capabilities and readiness

| Evidence | Establishes | Does not establish |
| --- | --- | --- |
| workspace_status succeeds | Access to the named workspace | Every channel is configured |
| Contacts available | Contact tools available | Every record has usable email |
| Email feature access | Email features permitted | Verified sender/domain or delivery |
| A shared/default domain is displayed | A default value exists | A customer-owned dedicated domain is assigned |
| social_accounts_list | Account inventory and capability flags | A particular post will publish |
| Send submission accepted | Request accepted | Recipient delivery |

Email readiness is currently unknown in workspace_status. defaultEmailSender is the current authenticated-user profile default, not proof of provider sender/domain verification. No supported tool enumerates verified domains, provider-verified senders, or the automatic-footer toggle. Unknown is neither configured nor disconnected.

## Email setup
Open the returned workspace nativeUrl, then Settings → Email Services. Inspect dedicated-domain inventory, verification, and sending assignment. A populated default-domain field is insufficient. Confirm browser and tool workspace match.

Use the authenticated-user From default unless the user requests another sender; use any explicitly requested Reply-To. Provider verification/setup remains separate. DNS alone cannot establish account assignment, and signup email or a historic template does not verify a sender.

Without browser access, explain the missing fact and provide the account link. Distinguish user confirmation from independently observed verification. Do not request SMTP passwords or API keys.

An authorized verification send tests a particular path at a point in time. It does not guarantee future delivery. Sending is not needed merely to discover tools.

## Social setup
Call social_accounts_list. Check posting/statistics and expired/active status independently per account. Use social_connections for setup or reconnection. Content/media requirements still apply to a posting-capable account; read guides/social.

## Availability
Authentication failure: use existing client connection controls.
Rate limit/service failure: inspect the error; do not repeat uncertain writes.
Unsupported capability: follow its account-screen handoff.
Never manufacture a readiness result to bypass missing evidence.