Feature Request: Automatic Access to Anchor/Block Links for All Doc Content Blocks
K
Keith Adamson
I’d like to request a feature that allows users to reference any content block or header in a ClickUp Doc with a persistent, unique URL—similar to how page anchors work in web documentation.
Current Limitation:At present, block (anchor) links are only created and accessible after a user manually clicks “Copy block link” in the UI for each section. This makes it difficult and time-consuming to reference or share specific sections, especially in large or frequently updated documents.
Feature Request:Please provide a way for every content block or header in a Doc to have a stable, accessible anchor or block link by default—without requiring any manual UI interaction to generate it.
• These links should be available for all headers/blocks automatically, so users and integrations can reference any section at any time.
• The method of generation is not important; the key is that the links exist and are accessible for all content blocks/headers.
Benefits:
• Enables easy, scalable referencing and sharing of specific sections in documentation.
• Supports integrations, automations, and workflows that rely on stable anchor links.
• Reduces manual effort and improves consistency for teams managing detailed or structured Docs.
Thank you for considering this request! This would greatly improve documentation usability and efficiency for all ClickUp users.
Log In
Bryan Lovgren
Thanks for sharing, can you tell me a little more about your use case ?
K
Keith Adamson
Bryan Lovgren we document our feature sets in clickup docs - this contains all the stories and epics for a given list. The tasks represent the implementation/progress towards the deliver of the detail in the doc.
We want all the feature documentation in one spot - helps with refinement and discussion of the details.
This allows for a deeper direct link from the task to the relevant section of the document.
I'm trying to break the need for a changing details inside of ONE story, that affects other stories down the roadmap. If the details are embedded in the story that becomes very difficult to manage down the line. So our story tasks are super light weight and only describe the highlevel business case, but the implementation details live in the document.
*what would be even cooler is if you could surface a section of a document inside the task itself, but the content "lives" and is updated in the document