Share domains

Share a domain when several of your customers should send from the same branded address domain. The domain stays at organization level. Every namespace can read it and send from its senders, while each namespace keeps its own sending health and suppressions.

Share a sending domainCopy Anchor Link

Use an organization credential to create a domain with shared: true, or update an existing organization-level domain. A domain assigned to a namespace cannot be shared.

import { createClient } from "samva";

const samva = createClient({ apiKey: process.env.SAMVA_API_KEY! });

await samva.email.updateDomainConfig({
  id: process.env.SAMVA_DOMAIN_ID!,
  shared: true,
});

In the dashboard, open the domain's detail page and enable sharing. The Shared badge identifies a domain that every namespace can use. The CLI accepts --shared on domain creation, updates, and listing; the hosted MCP domain tools accept shared.

Verify the domain's DNS records before sending, following Verify your sending domain.

Send within a namespaceCopy Anchor Link

With a namespace credential, pass a shared sender in from just as you would pass an owned sender. The message and its recipients belong to the credential's namespace. Organization-wide suppressions and that namespace's suppressions apply; another namespace's suppressions do not.

A namespace can select a shared sender as its default through setDefaultSender. An organization credential can select the namespace explicitly. Sending without from then uses that namespace's default.

Shared domains and their senders are read-only to namespace credentials. Attempts to change them return 403 with a remedy: use an organization credential. Catch-all, forwarding, inbound endpoints, and the unknown-recipient mailbox remain managed by the organization.

Stop sharingCopy Anchor Link

Update the domain with shared: false using an organization credential. First replace every namespace default that points at a sender on the domain; Samva refuses to unshare while one remains. After unsharing, namespace credentials can no longer read or send from the domain.

Reputation on a shared domainCopy Anchor Link

Mailbox providers see the same sending domain across namespaces, so domain reputation is shared. Separate sending health and suppressions do not isolate that mailbox-provider reputation. Use separate domains when customers need separate domain reputations.