Company guide: from your site to a receipt

Set up a site, collect a separate consent decision and give your email provider scoped access.

For the company operating a product. You do not need to become an ESP to collect consent. Plan for access to your domain’s DNS and help from the developer who operates your backend.

1. Register the product and verify its domain

Use a Company workspace for your organization and add the website where consent will begin. Choose a recognizable application name and the exact HTTPS site URL. Follow the issuer’s DNS challenge to verify control of that host. Verification proves domain control; it does not create recipient consent.

Keep the application identity, consent/sender-domain authority and return URL explicit. Different sites or tenants may need separate application records and scopes. An existing receipt cannot be reassigned to a different sender by renaming a site.

In Emabled: use Company → Sites & apps and follow that application’s Setup steps. Its verified-domain registration path can prepare the application without a separate general support approval; the developer must still complete the signing, consent, domain-role and return configuration. The first-receipt implementation guide documents the actual API steps. The Deploy to Agents rollout included developer/operator assistance.

2. Connect an admitted identity method

Your application’s login identifies the person; the consent screen records a separate decision about email. XCIM can admit OIDC, OAuth with authenticated provider API verification, or EVP address-control evidence under the selected profile. Merely obtaining an OAuth token or logging in does not authorize marketing.

Google was the OIDC provider used in the Deploy to Agents test. Microsoft or another provider needs its own supported adapter, configured issuer/client checks and an end-to-end test; this report does not establish those integrations. EVP remains experimental in Emabled’s vendor-origin handoff; hosted EVP consent and a public EVP end-to-end result remain unavailable. Check Emabled’s delivery capabilities and its EVP/XCIM implementation guide before selecting that path.

3. Prepare the consent people will see

Define the identified sender, communication types, plain-language explanations, frequency and privacy policy. Explain optional and required choices accurately. Optional choices start unselected. Keep sign-in and marketing permission distinct.

In Emabled: open the application’s Consent screen. Edit its options, logo and colors, or request a proposed design from a page on the verified domain. Review the proposal, apply it to the draft, save and then publish. A design preview is not a publication or a consent decision.

Changed consent text needs a verified backend signing endpoint. A saved draft can therefore be valid while publication still needs developer setup. Appearance-only edits can reuse the existing signed text. Follow the editor’s status and the signing setup guide. Do not paste a private application key or OAuth client secret into the console. The Deploy to Agents test preserved its signed screen; it did not publish its edited draft.

4. Run one real consent journey

  1. Start a new consent session from your site with the intended application and manifest.
  2. Have the person verify their identity, review the issuer-hosted screen and make their own decision.
  3. Return to the exact configured HTTPS route. Your backend checks the receipt signature and its application, manifest and session binding.
  4. Confirm the recorded result in the application’s Activity view. Test rejection, withdrawal and replay handling separately before expanding use.

Store backend keys durably with the least access required. A key that only exists in a temporary process will be lost when it restarts. Deploy to Agents used non-exportable Cloud KMS Ed25519 signing; another secure signing system may satisfy an implementation’s requirements. This is not a universal requirement to use Google Cloud.

5. Give your ESP access to this application

Ask the ESP for its provider code. In Emabled’s Company → Email providers, select the application, consent configuration, purpose and sending domain. Set an expiry, a per-validation row limit and a total row budget, then review the exact scope before confirming. Send your list to your provider through your agreed secure channel; the provider code does not transmit that list.

The ESP then chooses your authorized site and uploads the CSV. Access lets it evaluate evidence, not create consent or send outside the recipient’s permission. Domain authority, backend credentials and provider access have separate expiry dates. Review or revoke access when the relationship changes.

What “done” means

Your site can obtain and verify a receipt, the intended ESP can evaluate the correct application and you can interpret both the permission result and any unavailable public evidence. A connected site, valid signature or matching list row alone does not establish full public XCIM verification, message delivery, legal compliance or a production trust network.

Read what was actually verified for Deploy to Agents · Read the consent protocol

Latest specification · draft-saez-xcim-04

Experimental individual Internet-Draft. A bounded C01/SR01 testnet pilot verified consent reuse and revocation on 26 October 2026; production readiness remains open.