Skip to content

Workspace setup

Use this setup once for a new workspace, then follow the guide for the first workflow you want to prove.

Open the workspace switcher and confirm that you are working in the intended workspace and brand. Data such as documents, audiences, emails, and sending settings can be brand-scoped, so check this before importing or creating production material.

In Settings → Workspace, review the workspace name and operational contact details. In Settings → Brands, confirm the brand name and company information that will be used by your team and, where configured, in email footer and sender workflows.

Open Settings → Members and invite the smallest group needed for the first proof:

  • an owner or admin who can change workspace and sending settings
  • the person creating the email, content, or integration
  • the person responsible for final review

Decide who owns sending-domain changes, audience decisions, and final approval. One person may hold more than one role on a small team.

Go to Brand → Knowledge Base and add a small set of current, trusted sources. Then review Brand → Brand Voice. Start with:

  • two or three examples your team would still approve
  • current positioning or product messaging
  • approved proof points and terminology
  • any claims or phrases that require special review

Follow Build your brand foundation for the complete process.

Choose one:

  • Email marketing: deliver a test broadcast to an internal list.
  • Loop: prepare and apply one useful draft or revision.
  • Application integration: send one real test record through a server-side webhook.
  • Website data: install the Connector and confirm events arrive.

Do not connect every source at once. A single end-to-end proof gives you a known-good baseline.

Before inviting more people or using a production audience:

  • enable two-factor authentication if required by your organization
  • confirm who can manage members, billing, integrations, and sending
  • configure a verified sending domain before production email
  • confirm unsubscribe, bounce, complaint, and suppression handling
  • store webhook or integration credentials only in approved secret storage

Your first operator can answer all of these:

  • Which workspace and brand am I changing?
  • Which source material should generated work rely on?
  • Who owns the audience and final approval?
  • Which domain will send the email?
  • How can I verify that the first send or data connection worked?

Next, follow the email marketing quickstart, Loop guide, or integration overview.