Overview

Once you have designed your form/workflow, set up integrations and tested thoroughly you are ready to share, or publish, your form to end users. The sections in this page explain how your users will access your forms and workflows. Before you start, review the Best Practices for Publishing Forms/Workflows from Development to Production and the topics below.

Set Visibility

Set the visibility of a form/workflow from either the Forms and Workflows Homepage or via Access Control in the Form/Workflow's Settings mode.

Other Permissions

The designer can set other permissions via the Access Control wizard such as roles and users that can edit the form/workflow, view/edit submissions, view the audit trail or be designated as workflow administrators.

Access Control settings set by the designer are retained when you download/upload a form/workflow/project to another designer user in the same or different tenant and when you copy a form/workflow.

Deploying to Production

You can publish any form/workflow regardless of the Who can start the form/workflow? permission. Publishing involves sharing your form/workflow with users (e.g. via a share URL, embedding in portal, or embedding in your website). Set the Deployment State to "Production" via the Form/Workflow Settings or the Action Menu to remove the watermark and (for Cloud customers) begin counting submissions towards your license.

Editing Forms/Workflows in Production

If you set the form/workflow visibility to anything other than "Designer/Owner only" and users have begun submitting it, you'll need to use caution when modifying your form. If users access it while you are editing it, they will see error messages indicating that the page is being refreshed or that the form is invalid.

Please see the Administrator Best Practices for Updating a Form/Workflow in Production.

Browser not supported