How do I distribute a form to connected accounts?
Last updated: November 2, 2026
Send a form from your platform account to your connected accounts, choose whether new versions go live automatically or wait for the account, and confirm it landed.
Before you start
Your account is a platform account. You'll see
Connected AccountsandBulk connectat the top of your sidebar.The form has a published version on your platform account. See π Understanding forms if you're not yet familiar with form versions.
Distribution follows the mode you're in. Work in live mode unless you're testing. See π Understanding test mode.
Pick a distribution mode
Each form has one setting per connected account. Choose the mode based on who should decide when a new version goes live.
Mode | What the connected account gets |
|---|---|
| Each new version you publish is published and deployed in the account automatically. |
| Each new version arrives as a draft. It goes live once the account publishes it. |
| No distribution setting. The account keeps any copy it already has, but won't receive your updates. |
Distributing a form also gives the account access to the form, and copies the form's expiration rules. The account's own expiration rules for that form are replaced by yours.
Distribute one form
Go to
Formsand open the form.Click the
Connecttab.You'll see every connected account, with its
Distribution mode,Deployed version, and lastDistributionresult.Set the
Default distribution mode. ChooseAuto DeployorManual Deployif every account you connect from now on should get this form, orDon't distributeif not. This doesn't change accounts that are already connected.Select the checkboxes for the connected accounts you want to change.
In the bar that appears, choose a mode in the picker and click
Apply.The
Distributioncolumn showsDistributing, thenDistributedonce the form is in place.
[SCREENSHOT: a form's Connect tab with two accounts selected and the bulk bar showing the mode picker, Apply, Deploy now, Recall, and Remove distribution]
The same bar has three one-time actions:
Deploy now: sends your current published version immediately and overwrites any edits the account made. The mode doesn't change.Remove distribution: stops sending updates. The account keeps the form, its access, and the version it's running.Recall: withdraws the form. The versions you deployed are deprecated in the account and its drafts are deleted. Tasks already assigned to candidates keep their version.
To see every form's setup at a glance, open the Connect tab on the Forms list. It shows each form's default mode and how many accounts are on Auto Deploy and Manual Deploy.
Distribute several forms at once
Click
Bulk connectin the sidebar and open theFormstab.Under
Select forms, check each form to include.Under
Select accounts, check each connected account to include.Under
Choose action, pickSet distribution mode,Deploy now,Remove distribution, orRecall.With
Set distribution mode, the picker starts onEach formβs default, which connects each selected account at that form's own default and leaves accounts that are already connected alone.Check the impact line, then click the button at the bottom to apply.
A recall in test mode also affects live mode. A form version's status is shared between test and live, so recalling in test mode deprecates the same versions wherever the connected accounts run them in live mode, and deletes their drafts. Onboarded asks you to confirm this before it runs. It can't be undone.
Verify
Go to Connected Accounts, open an account, and click its Forms tab. Each form you distributed shows its Distribution mode, the Deployed version, and Distributed in the Distribution column. Outdated next to a version means the account isn't on your latest one yet. That's expected for Manual Deploy until the account publishes the draft.
To see it from the account's side, click Impersonate Account and open the form from their Forms list. With Auto Deploy, your version is already published. With Manual Deploy, it's waiting as a draft.
If something didn't land:
The result is
Failed. ClickView activityon that row to see the error, thenRetry. A common one isThe account is missing a custom attribute this form uses.TheFailed Distributiontab onConnected Accountslists every failure from the last 14 days.The result is
Changed by connected account. That's not a failure. The account published its own version.Deploy nowreplaces it with yours.A new account didn't get the form. The default only applies to accounts connected after you set it. Apply the mode to that account directly.
Form Distribution strategies are no longer in the sidebar. Each form's Connect tab is now the place to see which accounts receive it and how, so check it if you're unsure how an account is set up.