ClickUp Relationships: Link Tasks, Docs, and Lists

ClickUp relationships are how you connect work that belongs together when one task does not block the other. A wireframe and the copy task, a meeting and the tasks you mentioned in it, a client and every open request: Help's own examples are references, not a sequence. Linking is on every plan. You can attach up to 500 tasks to a single task. Guests with edit permissions and above can manage those links. You can only open a linked task or Doc if you already have permission to view it.

If the real rule is "this cannot start until that finishes," use a dependency instead. Dependencies can reschedule dates. A plain link does not. The ClickUp hub is the index for both, plus the views where the columns show up.

What are ClickUp relationships?

Help treats "link tasks" as one kind of relationship: tasks that relate, and are not dependent. The link lets people move between the work and see the rest of what is relevant. It does not apply the rules dependencies use. Help names rescheduling dependencies as an example of a rule that linked tasks ignore. Change a due date on one side of a link and the other side stays where it is.

You can also link a Doc. From the task, the add-links control asks you to choose Task or Doc, then search. That is the light connection between a brief and the tasks that came out of it. ClickUp Docs is where the page itself lives.

Archived tasks on a relationship are hidden until you click Show under the table. Reload the task and they hide again. If a link looks missing, check the archive before you create a duplicate.

How do you link tasks in ClickUp?

Help lists more than one place to add the link.

From the task:

1. Open the task you want to link from.
2. Click the Add links icon on the right.
3. Choose Task or Doc.
4. Search or browse, then click the item.
5. Open Related items on the right to see the links.

From the Related section lower on the task, use the plus icon, or Relate items or add dependencies if nothing is linked yet, and pick the relationship type. The right sidebar's Related icon can add related items too. Help says dependency relationships cannot be added from that sidebar path. Use the Related section, the task ellipsis under Relationships, or the slash commands in the dependencies guide for blocking and waiting.

From List view, select the tasks, open More on the Bulk Action Toolbar, and click Link Tasks. Search for the task that should sit on the other side.

An automation can add a link with an Add Relationship action set to Link Task, or by linking a new task back to the task that triggered it. ClickUp automations are the setup for that. Build it after the manual link is a habit, not before.

To remove a link, open Related items, hover the task, scroll to the x, and click it. Either task can drop the link.

Help's examples are worth copying as a rule of thumb:

• Link a wireframe task to the content task so design can see which sections still need graphics.
• Link the tasks you cited in a meeting so people can find them without replaying the notes.
• Link a client's requests to the client record when you want one place to open.
• Link the support tasks that belong to one customer issue.

A sales pipeline uses the same idea with more structure. The ClickUp as a CRM guide covers contacts, accounts, and deals as tasks, with relationship columns on List view.

What is a ClickUp Custom Relationship?

A Custom Relationship is a named link with a type you choose. Help says Custom Relationships are on every plan. Guests cannot create them. Guests with edit or full edit permissions can remove one that already exists.

Create one from the Related icon: plus, New custom relationship, a name, the type, and Create. Turn on Create rollup fields if you want columns from the other List. You can add rollup fields later. The task ellipsis has the same flow under Relationships, then Create Relationship.

After it exists, open Related, plus, pick that Custom Relationship, and search by keyword or task ID. Help says a List-to-List relationship is only visible in one of the Lists. If you cannot find it, open the other List before you build a second relationship with the same name.

Automations can set a Custom Relationship when they create a task or subtask, or through the Add Relationship action. You pick an existing Custom Relationship and a task to link to the trigger. The relationship has to exist first. An automation cannot invent the name.

Recurring tasks have a gap Help states directly. Tasks from a specific List are not supported on recurring tasks. When the task recurs, those links are not copied onto the new task. Add them again. The recurring tasks guide lists the other fields you can choose to copy, including relationships in general.

How are relationships different from dependencies?

Use this split before you add either one.

Dependencies are also on every plan, and they are not available in the mobile app. Relationships are the reference. Dependencies are the sequence. A project that only uses links will look connected and will still let someone finish step 3 before step 1. A project that only uses dependencies will show the sequence and will hide the "this is the same client" grouping. Most Lists need a few of each, not a web of both on every task.

List view can group by custom relationships, which is why the named link is worth creating when you filter a board by client or by account. Custom fields still hold the data that is a property of the task itself, such as a deal amount. A relationship points at another task. A field stores a value.

Where should you start?

Start with plain task links. They are on the free plan, they take a minute, and the 500-task ceiling is far above a normal task. Add a Custom Relationship when the same kind of link shows up often enough to need a name and, for List-to-List, a rollup column.

Skip Custom Relationships on day one if you are still deciding the hierarchy. A relationship to a List you will rename or replace is stuck: Help says the selected List cannot be changed later. Build the Lists first. The hierarchy guide is Spaces, Folders, and Lists.

ClickUp is a reasonable place to keep those links because tasks, Docs, and the views sit in one Workspace. A team that only needs a simple board, and rarely opens a related card, will move faster in a lighter tool. If the work is a chain of blockers plus a set of references, turn on a handful of links, keep dependencies for the real blockers, and leave the rest unlinked.