Platform embedded signing with Atlas

If you sell software to many customers who each need their own signing history, you want platform tenancy: one Atlas org for you, many child accounts for clients, billing rules you control.

Atlas platform mode is REST-first in v1. MCP stays user-scoped. Plan your agent flows accordingly.

> Share: "Embedded signing should keep your brand and your billing model, not redirect users to a second product."

Connected accounts

Provision a client with POST /api/platform/connected-accounts. Atlas returns an external id like ext_acme. Every downstream call includes:

Atlas-Account: ext_acme

The child account gets its own envelopes, credits policy, and webhook endpoints depending on how you configure billing mode.

Billing modes

platform_pays means you consume credits from your platform balance when the child sends. child_pays pushes purchase to the child org. See billing modes for how Stripe attaches.

Model margin per client send when you bundle signing into a higher-tier SaaS plan. Platform keys follow the same per-send credit model as direct users.

Embed the review step

Even in embedded flows, Atlas keeps review-before-send for new uploads. Your UI can deep-link users to review_url or iframe the review page if your security model allows it. Signers still only get email after Send.

For fully headless dispatch, REST supports auto_send: true at create when your product owns compliance UX and legal approved the template shape.

First client onboarding: walk review manually. Repeat document types: pin templates and enable auto-send when the shape is proven.

Webhooks per tenant

Set webhook_url per envelope or standardize in your integration layer. Verify X-Atlas-Signature with the API key that created the envelope. Route events to the correct client workspace in your database using metadata.client_reference_id or your own mapping table.

Store external_id beside your customer row in Postgres or Salesforce. When envelope.signed fires, look up the tenant before you file the PDF.

PDF and DOCX

Upload paths accept both formats. DOCX converts to PDF for signing. Field detection runs the same pipeline as single-tenant users.

Security checklist

• Store platform keys server-side only.
• Never expose child API keys in the browser unless you intend direct client access.
• Scope support staff with org roles. See teams and permissions.
• Load-test webhook endpoints before you onboard a client with hundreds of simultaneous matters.

White-label and branding

Org-level branding settings control sender name and logo on emails and the sign page. Child accounts can inherit or override depending on how you provision them.

If your customers expect a fully custom domain on sign links, confirm your rollout plan with support before you promise a specific hostname in sales decks.

Example provision call

curl -X POST https://atlaswork.ai/api/platform/connected-accounts \
  -H "Authorization: Bearer PLATFORM_KEY" \
  -H "Content-Type: application/json" \
  -d '{"external_id": "acme_legal", "name": "Acme Legal"}'

Use the returned external id on every child envelope create. Keep platform keys in your secrets manager, not in front-end env vars.

Support playbooks

Give each child a contact who can open review links. Platform mode does not remove the human Send step for new uploads. Train customers on review-first flow during onboarding so they do not expect instant signer email from API calls alone.

Pilot rollout

Start with one friendly customer on platform_pays. Run ten test envelopes through review and sign. Confirm webhooks, credit consumption, and signed PDF storage in your app before you flip billing to child_pays or open self-serve provisioning.

Margin and pass-through pricing

If you bundle signing into a $99 per month SaaS tier, model credits per active customer, not per seat in your company. A client sending forty contracts per month at $1 each is $40 in Atlas cost before support time. Price the bundle so envelope-heavy customers do not erase margin.

Pass-through billing (child_pays) pushes purchase to the client org when you want zero credit risk on their volume spikes.

FAQ

Is MCP available per connected account? Not in v1. Use REST with Atlas-Account for child tenants.

Can children use auto-send? Yes on REST when your integration and legal process allow it. New uploads still default to review.

Where is the platform quickstart? Read platform quickstart and connected accounts.

How does Atlas compare on price? See Atlas vs DocuSign if you pass per-send fees through to customers.

Get started

• Platform overview
• Platform quickstart
• Sign up to test single-tenant flow first

Related reading

Next reads that match this topic: DocuSign embedded signing and Atlas platform …, Blockchain document signing without the hype, and DocuSign API alternative for developers.