Build reusable linked modules

Last updated: November 10, 2026

Who can do this: Super Admins and Creators

A library module is a group of tasks you build once in the Library and link into any number of playbooks. When you edit it in the Library, every playbook that links it gets the change. If drafts are turned on, playbooks get the change once the draft is published.

Before you begin

  • Drafts and publishing for library modules are available when they're turned on for your organization. If you don't see Edit and Publish in the module editor, contact your OnRamp team.

  • Contributors can't link modules into playbooks. To link one, you need edit access to the playbook and read access to library modules.

Create a module

  1. Go to Library > Modules and select Create Module. OnRamp creates a module named Untitled Module and opens it in the module editor.

  2. If drafts are turned on, select Edit to open a draft. You can't change the module until you do. If a draft already exists, select View draft, and then Edit draft.

  3. In the editor header, rename Untitled Module. Module names must be unique.

  4. On the Task List tab, add your tasks.

  5. Optional: On the Settings tab, set Customer Portal Module Name, Exclude weekends for task due dates, Work Order and Data Fields.

  6. If drafts are turned on, select Publish.

Without drafts, your changes save as you make them. With drafts turned on, your edits stay in the draft until a Super Admin or Creator publishes it.

Customer Portal Module Name is what customers see in the portal and in email notifications. Leave it blank to show the internal module name.

Work Order controls whether tasks must be done in sequence: Any Order (the default), Customer Tasks Sequential, Internal Tasks Sequential or All Tasks Sequential. In a playbook, you can change it only on a module that isn't linked. On a linked module, it's shown but can't be changed. In a project, you can change it unless the project has ended or you can't manage its modules.

The module editor also has Merge Fields and Automations tabs. To add modules to projects automatically, see Module Automations.

Link the module to a playbook

  1. Go to Library > Playbooks and open the playbook.

  2. On the List tab, select + Module, and then select Add Linked Module.

  3. In the Choose from Library dialog, select your module.

  4. Select Add to Playbook.

The module appears in the playbook. If you're allowed to open the library module, you see a green Linked Module label on it. Select the label to open the source module in the Library. People who can't open the library module don't see the label. You can't add tasks inside a linked module, so add playbook-specific tasks in the playbook's other modules.

To see where a module is used, open it and select the Linked Playbooks tab. It lists the playbooks under Active and Archived, each with a count.

How edits reach playbooks and projects

Without drafts, edits to a linked module reach every playbook that uses it as soon as they're saved. They reach only projects created afterward. The editor header shows how many playbooks the module is linked to.

With drafts turned on, linked playbooks keep the published module until someone selects Publish and confirms in the Publish module dialog. The dialog lets you choose what happens to active projects that hold the module:

  • Update N projects now pushes your changes into those projects. It runs in the background, and you can undo it from the module's Activity for 14 days. The confirm button reads Publish and update N projects. Tasks that are started or done aren't touched, and edits a project team made are kept unless you choose otherwise.

  • Only use the published module for new projects leaves projects in progress unchanged.

A Work Order change is tracked as a Task order change.

To throw away a draft, select Delete draft. All changes in the draft are deleted, and the module goes back to the published version.

Change a linked module in one playbook

Open the module in the playbook to see its options:

  • Unlink Module leaves the module and its tasks in the playbook as they are. They stop getting updates from the library module and become editable in the playbook. You can't undo this.

  • Remove Module removes the linked module from this playbook. It doesn't affect the module in the Library.

To start a new module from an existing one, go to the module's Settings tab and select Make a copy. The copy goes into your Library, so you can change it without affecting the original.

Archive or delete a module

On the module's Settings tab:

  • Archive this Module archives the module in the Library and takes it out of the playbooks that link it. Projects keep the copies they already have. For a linked module, you choose to Leave an un-linked copy of this Module in all Playbooks or Remove this Module from all Playbooks that contain it. To bring the module back, select Un-archive Module, and then select Unarchive this Module.

  • Delete this Module permanently deletes the module's tasks, subtasks and data field values. It removes the module from the Library and from the playbooks that link it. For a linked module, you first choose to leave an un-linked copy of it in those playbooks or remove it from them.

You can also add library modules to active projects with Add from Library. See Using the Project Gantt Chart.

Related articles