Feature Requests

When reading or writing Doc pages via the API or MCP server, only text/md (Markdown) and text/plain are supported as content formats. This means that any rich formatting applied in the ClickUp editor — such as colored text, callout blocks, banners, column layouts, and other editor-specific elements — is lost when a page is written back via the API or MCP. This creates a real problem for AI assistant workflows (e.g. using the official MCP server with Claude or other LLMs): if a Doc page has been carefully formatted in the ClickUp editor, any AI-assisted update to that page will strip all of that formatting, since the only write path available is Markdown. What I'd like: Either (or all) of the following: * idea 1: A richer content format option (e.g. text/html or a ClickUp-native rich text AST) for both reading and writing Doc pages, so that formatting round-trips cleanly. * idea 2: A read-only rich format so that the original formatting can be fetched and preserved when writing back — even if writes remain Markdown-only. * idea 3: An API / MCP tool to insert in a doc at a certain position, so we can just update selected part without rewriting the whole doc (added value: likely to save tokens) Use case: Using the ClickUp MCP server with an AI assistant to append or update content in Doc pages that were formatted in the ClickUp editor. Currently, doing so risks destroying the existing visual structure of the document.

Problem Description Currently, ClickUp Docs displays LaTeX math formulas only as raw source code. For example, entering a matrix: \begin{bmatrix} a & b \\ c & d \end{bmatrix} does not render a visual matrix; the plain text is shown instead. This makes mathematical expressions nearly unreadable and forces users to take screenshots or generate images of formulas externally, breaking the writing flow. The lack of math rendering is a major reason why engineering, data science, and research teams cannot consolidate their documentation fully into ClickUp. Technical Feasibility Rendering LaTeX math on the web is a solved problem with mature, lightweight JavaScript libraries: KaTeX (recommended) – Developed by Khan Academy. Extremely fast, small bundle size, supports a large subset of LaTeX including matrices (\begin{bmatrix}...\end{bmatrix}). Used natively by Notion as its math engine. MathJax – Offers the most complete LaTeX support, including complex AMS packages. Slightly heavier than KaTeX but highly reliable. MathLive – A more advanced Web Component that provides an editable math field (<math-field>) and a static renderer (<math-span>), supporting 800+ LaTeX commands with built-in accessibility. All three can be loaded via npm or CDN (e.g., jsDelivr) and require no server-side processing. The typical implementation pattern is: Users type LaTeX source between delimiters ($...$ for inline, $$...$$ for block) in the editor. In preview/read mode, the rendering layer scans the content and replaces the source with SVG/HTML output using KaTeX or MathJax. Edit mode could optionally use MathLive’s <math-field> to provide live preview while editing. Competitive Landscape A comparison with tools that teams often use alongside or instead of ClickUp: Notion – Full native LaTeX support powered by KaTeX. Supports inline formulas (via Ctrl+E or $...$) and block formulas (/math), including matrices. Considered the gold standard for technical notes. Confluence – No native LaTeX renderer. Users must install and pay for third-party Marketplace apps (e.g., LaTeX Math for Confluence) that use MathJax, adding cost and administrative overhead. HackMD – Native LaTeX in Markdown documents, with real-time collaborative editing and instant rendering. Widely used by technical writers. Obsidian – Native LaTeX formula rendering via built-in MathJax. A benchmark in the personal knowledge management space. Dropbox Paper – Has robust LaTeX math rendering. Frequently cited by ClickUp users as a reference implementation for how Docs could work. ClickUp Docs – No math rendering engine available. This is the current gap. Testing Environment Platform: Web Browser: Microsoft Edge 147 ClickUp Docs version: Current production version Test date: 2026-04-26 Steps to reproduce: 1. Create a new ClickUp Doc 2. Paste the LaTeX matrix code \begin{bmatrix} a & b \\ c & d \end{bmatrix} 3. Observe that only raw source text is shown; no rendered matrix appears Recommended Approach Phase 1 – Integrate KaTeX and support $...$ (inline) and $$...$$ (block) delimiter syntax to cover common math expressions (matrices, fractions, integrals, sums, etc.). Phase 2 – Add a visual formula editor panel to lower the barrier for users unfamiliar with LaTeX syntax. Follow the interaction model proven by Notion: a keyboard shortcut inserts a math block, users edit LaTeX source, and the output renders in real time. Business Impact The absence of math rendering prevents many engineering, data, and research teams from adopting ClickUp as their single documentation hub. These users are forced to maintain documents across both ClickUp and other platforms (Notion, Obsidian, Confluence with plugins, etc.), fragmenting workflows and reducing the value of ClickUp Docs. Multiple community requests (some dating back to 2019) describe this as a “deal-breaker” – closing this gap would unlock a significant, technically skilled user segment.

Before ClickUp 4.0, guests with edit permissions were able to create new Docs directly in the Docs Hub, even when the document was not linked to a Space, Folder, List, or Task. After the 4.0 update, guests can still view and edit existing Docs, but they can no longer create new ones in the Docs Hub. This change was not clearly communicated and broke established workflows that relied on guest collaboration. We are requesting the ability to allow guests to create new Docs in the Docs Hub again, restoring the previous behavior or providing a configurable permission for workspace admins. Problem / Why this matters Many teams use guests for: External consultants Partners Auditors Designers Engineers or specialists working on documentation In these scenarios, guests are expected to: Create meeting notes Draft procedures (SOPs) Propose documentation Collaborate asynchronously Blocking Doc creation forces teams to: romote guests to full members (higher cost) Create Docs on their behalf Use workarounds like templates and duplication This negatively impacts collaboration, governance, and efficiency. Expected behavior Workspace admins should be able to: A) Allow guests to create Docs in the Docs Hub OR B) Enable a specific permission like: “Allow guests to create Docs” This permission could be optional and disabled by default for security-conscious teams. Actual behavior (ClickUp 4.0) Guests can edit existing Docs Guests cannot create new Docs in Docs Hub Docs created by guests before 4.0 still exist No clear permission toggle or documentation explains the change Business impact Increased friction in collaboration with external contributors Higher costs due to forced member upgrades Reduced adoption of ClickUp Docs for shared documentation More “manual proxy work” by internal team members Additional context This feature existed and worked well before ClickUp 4.0. Restoring it (or making it configurable) would align ClickUp Docs with real-world collaboration needs while still preserving security controls.

Markdown is not sugar over a mystery backend format. All text needs to be all genuinely markdown all the way. If I paste markdown from Github or wherever it should work (to the extent the markdown flavor matches). If I select text in ClickUp and paste in Github or Slack it should show up as markdown, not flat text with formatting stripped.

When having a public document with many pages that everyone can view, I would wish you could add the feature of having one page that should be private and shared with a limited number of people.

This is just dumb. Can we PLEASE get this fixed!? Also reported: https://feedback.clickup.com/feature-requests/p/comment-on-code-comments https://feedback.clickup.com/feature-requests/p/ability-to-comment-on-code-blocks-in-docs

Filtered task lists to be embedded into Docs

I use DOCs a lot to record meeting minutes for different businesses. I would like to be able to assign different editing permissions per page. For example: For the entire document, I would like to assign everyone viewing permission. And for some pages, I would like to grant editing permission to specific people.

I have a huge wiki document with multiple subpages nested into a neat hierarchy. I’d love to be able to export a subsection of a doc but also include its some pages. For example, i have a section in my wiki document full of SOP’s. I’d love to export all the SOP’s under there in to one markdown or HTML file. Right now, i have to export either the entire wiki, and remove what I don’t want from a massive doc. Or download each subpage manually and then merge them manually. It’s time consuming especially after i spent so much time organizing all my content in a neat hierarchy

there are short cut keys for changing text to headers, and one header size to another - but none for header to text. with all of the ai chats i'm copy pasting over, it slows down work flow having to go back, highlight the header, select text manually. I understand i can paste without formatting, but then I have to go and short cut keys on all the headers i wanted to keep intact. <3 clickup