Library

Bundles distribute reusable configuration across workspaces. Each published version contains selected Workflows, Forms, or Sites. Member records, Chats, and credentials stay in their workspace.

Create and publish

1. Open Library in the publishing workspace.
2. Choose Create Bundle in the Library header.
3. Open the Bundle's Settings tab. Set its name, write its description with the Markdown editor, and select its contents.
4. Save your changes, then Publish. Use the Markdown editor for release notes when consumers need to know what changed.

Library → Mine lists the Bundles this workspace owns, drafts and published.

The Workflow picker shows the workspace's Workflows. A published Workflow can be picked without publishing it again. A Workflow that has never been published shows Unpublished. Open it from Workflows, publish it there, then return to the Bundle and add it.

File Access includes the selected Files and Folders when you have permission to read and share them; Member label actions include their label definitions. Connected documents, Chart Files, custom access roles and contributors remain unsupported. Workflows published before this support was added need to be republished, then added using the new revision.

If a Workflow uses an unsupported resource or you lack permission to include a dependency, saving the Bundle names the Workflow and explains the refusal; that Workflow is not added. Publishing checks that you can use every Form the Bundle's Workflows use. Included Workflows, Forms and Sites stay visible in their pickers with a disabled Already included label.

Dependency details explain what needs correcting, without internal identifiers. Open resource to review sharing opens the affected File or Folder when you lack permission to share it; ask its owner for that permission. When you cannot read a dependency, ask its owner for access. File and Folder links open their details in Files. Workflow changes open the editor, where you can replace missing resources or correct label actions, then publish a new revision. The Bundle does not change sharing permissions for you.

When a required Form still exists, Add [Form name] to Bundle includes its definition. A deleted source Form needs restoring or replacing in the Workflow before publication. After correcting a dependency, select Check again to refresh the Workflow's eligibility.

If stored File contents cannot be read right now, Retry save repeats the Bundle capture with your current contents. It keeps unsaved name and description edits for the normal save. If the error continues, ask an administrator to check storage access. Upload a replacement only when the error confirms that saved contents are missing.

Share within your organization

Publish the Bundle, then open Subscribers and choose Share. An organization admin can make it available to every workspace in the publishing organization. Managers in those workspaces choose where to install it.

Sharing is limited to the publishing organization. Sharing a draft is unavailable because there is no version to install.

Sharing grants access; the recipient still chooses whether to install. Source visibility and independent copying are part of the current sharing experience.

The Subscribers tab lists subscribers by name and version. Manage opens the Bundle in an accessible subscriber workspace. Revoke removes a grant after confirmation.

Install and update

In the receiving workspace, open Library → Available and choose Install on the Bundle card. A Bundle that requires an Inbox selection opens setup first. Installation always starts with the latest published version. Once installed, the Bundle moves to Installed; Open leads to its settings. Earlier versions remain available for inspection under Versions. The installed version lists links to its local Workflows, Forms, Journeys, and Sites.

Installed shows subscriptions and available updates using the same cards as the Available catalog. Open a Bundle to enable or disable Auto-update, complete any missing setup, or take an update. The switch asks for confirmation and explains the consequences. When auto-update is enabled, compatible Form changes apply automatically; breaking changes require local reconciliation before the subscription advances. An unsuccessful update retains the previous usable version.

Workflows and Journeys in the same Bundle use one shared Member Label when they refer to the same source label. Publisher updates apply only while your local label matches the installed definition. Conflicting local edits stop the update instead of being overwritten. Earlier Journey installations retain their existing Labels and Member associations when upgraded.

To stop future updates, open the Bundle's Settings and select Detach. Existing Workflows, Journeys, Forms, Sites, records, and Assignments stay in the workspace. You will need to maintain the retained resources yourself. The Bundle returns to Available, where you can install its latest version again.

To customize a Workflow independently, use Clone Workflow. The copy does not receive publisher updates.

Organization Library

The organization's Library lists its published and draft Bundles, versions, publishing workspaces, and subscriber counts. Open a Bundle to manage it in its publishing workspace when you manage the publishing workspace. The workspace link opens that workspace.

Creating, publishing, sharing, and managing subscriptions require the relevant workspace management permissions. Organization membership alone does not grant access to edit every workspace's Bundles.

Recover a removed Form

The installed Bundle's Settings identify missing and archived resources by name. For a deleted Form, Reinstall Form recreates its definition from the installed version and repairs its installed references. It does not restore deleted records or advance the Bundle version. Restoring requires Form write permission as well as Bundle management permission. For an archived Form, follow Restore from archived Forms and restore the existing Form there.

Recover Workflow resources

Open Library → Installed, open the Bundle, then select Settings. Its readiness details name the affected Files, Folders and Member Labels.

• Missing: select Restore resources for [Workflow name] to recreate missing resources from the version you already installed and repair the Workflow references. This keeps the installed version and leaves changed resources intact. You need Bundle management permission, permission to edit Files and Folders for those resources, and permission to edit Members for Member Labels. A disabled button explains which permission is missing.
• Moved from its installed location: use Open Files or Open Labels to review the affected resource and restore its original structure. These links require permission to read the relevant area. Automatic restore does not move or overwrite existing resources.
• Changed: local File content or label details differ from the installed definition. The Local Workflow resource changes section is informational; these changes alone do not prevent the Workflow from running. Restore does not overwrite them.
• Republish required: the published Workflow did not package this dependency. Ask the publisher to republish the Workflow and publish a new Bundle version, then update the installed Bundle. Restore is unavailable for that Workflow until a complete release is installed.

Restoring uses the published resource definitions, not later edits in the source workspace. It does not recover deleted Form records or other Member data. For a removed Form, follow Recover a removed Form.