Feature Requests

We should have the ability to export all docs on a space / folder / list / basis in bulk instead of having to do them all individually.

Hi ClickUp team, Tasks can live in multiple Lists while having one Home List. Docs (including meeting notes) should support the same pattern: one home location, with the ability to reference/surface the Doc in additional Folders, Spaces, or Lists without duplicating it. Use case: A meeting notes Doc is auto-generated in a default location, but I need it visible in both the project Space and a team knowledge base. Currently I have to choose one location or duplicate it manually. This would make Docs a first-class organizational object on par with tasks.

ClickUp Docs allow users to copy a link to a specific content block. However, these links use the internal app.clickup.com URL and require the visitor to log in—even when the Doc itself has been publicly shared. This makes block links unusable in client-facing documentation, proposals, guides and knowledge bases. Expected behaviour: When a Doc or page is publicly shared, “Copy block link” should generate a public doc.clickup.com URL. Anyone with the public link should be taken directly to the relevant block without needing a ClickUp account. Existing links within a public Doc should remain inside the public version rather than redirecting to the internal workspace. Ideally, ClickUp should provide separate options for “Copy internal block link” and “Copy public block link.” Current behaviour: Make a Doc publicly accessible. Copy a link to a block. Add that link to text within the Doc. Open the public Doc while logged out. Click the block link. ClickUp redirects to a login page instead of the linked section. ClickUp already supports public Docs and block-level links independently. These features need to work together. A public document should not contain navigation links that unexpectedly force clients to create or access a ClickUp account.

I would like to have different permissions for different pages of a document, e.g. I only want my admin assistance to see certain pages

Description: As a long‑time ClickUp user, I truly appreciate the product's rapid iteration. However, I've noticed a common issue that affects all users (both individuals and teams): there is no centralized, transparent, and predictable channel to learn about the product's future direction and the cadence of regular updates. Currently, apart from major releases like 3.0 and 4.0, the timing of weekly or bi‑weekly patches and minor feature updates is inconsistent. Users have to piece together information from scattered sources – Canny for feature requests, the Changelog for past releases, official blog posts, and social media announcements. This fragmentation creates several problems: · For individual users: Sudden UI changes or new features interrupt workflows and force last‑minute learning, reducing personal productivity. · For collaborative scenarios: Team members get out of sync due to different update adoption times, making it hard to coordinate training or adapt to new workflows. · For long‑term planning: Without visibility into the product roadmap, users struggle to make informed decisions about adopting new processes or committing to the platform for future projects. My suggestion: Leverage ClickUp's own powerful Docs feature to create a dedicated, official page that serves as the single source of truth for all update‑related information. This page should include: A clearly stated release cadence – for example, announce that minor updates are released every two weeks (or monthly), so users know what to expect. (ClickUp already shares weekly changelogs and performance updates; making this explicit in Docs would be very helpful.) An integrated and enhanced product roadmap – ClickUp already has a public roadmap (e.g., on feedback.clickup.com ), but consolidating it into the official Docs with a clear structure like "Now / Next / Later" would greatly improve readability and show what's in progress, planned, and completed. Advance update notices – for upcoming important changes (especially UI tweaks or new features), post a brief preview 48–72 hours in advance on this Docs page, describing the scope and potential impact. Benefits of this approach: · Single source of truth – one official Docs page that users, sales teams, and customer success can all reference with confidence. · Increased transparency and trust – publicly sharing the roadmap and release cadence demonstrates that ClickUp listens to its users and is moving forward with purpose. · Better user planning – individuals can schedule time to learn new features, and teams can coordinate training and internal communications more effectively. · Showcases product momentum – a visible roadmap and predictable updates reinforce user confidence in the platform's long‑term viability. I hope the ClickUp team will consider using Docs to make product iteration more transparent and predictable. Thank you for listening!

What: Built-in signature requests for PDFs with signer roles/order, authentication (OTP/SSO or connector), reminders, tamper-evident signed PDFs and audit logs; option to sync signed copies to SharePoint. Why: We need formal approvals for SOPs/CAPA/contracts; external tools break traceability and complicate audits. Benefit: Keeps the full author → review → sign → publish lifecycle in ClickUp, improving compliance and reducing manual handoffs.

Thank you for v2. So many improvements to an already great app :) I would like to request that you please consider adding latex (math typesetting) to docs (and comments?). Maybe via https://www.mathjax.org/ or other (dropbox have a nice implementation as well in their new "Dropbox Paper"). Ideally, this could be a setting to be enabled per user so that text surrounded with '$' (or '$$' for an equation line) will be rendered by the math engine (i.e. mathjax). Thank you!

Synced blocks enclose any section of text/images/etc. that can then be copied elsewhere and can be edited in multiple locations and it updates everywhere. For example, if I write out a goal that I want to keep in front of me, I can add it to all relevant docs and task descriptions and if I make changes to it, it'll update everywhere else as well.

It would be really helpful if we could move existing documents to nested subpages. This would go a long way to making document re-organization simpler.

Hi, I would like to request a feature for document management that includes document review and approval processes. When a document is created and shared for collaboration, anyone with the link or access can edit and include their thoughts and ideas. Once a document is under review, it should be locked from further editing, and only individuals with review access should be allowed to make edits. After the review, the document will be sent to the approver, and upon approval, it will be automatically published in the assigned wiki folder or page. I am also interested in a feature that automatically generates document names according to a configured prefix or naming convention. Additionally, I would like an audit trail for each document for ISO and other compliance purposes.