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.

ClickUp Brain can now generate slides, but there is not a clear way for a Super Agent to own that workflow end-to-end. Admins cannot reliably instruct an agent to create a slide deck, apply company-specific formatting or brand standards, and then place the finished output into Docs for further editing and collaboration. This creates a gap between AI-generated content and team-ready deliverables. The output may exist, but it is not yet easy to operationalize inside enterprise workflows where teams need editable, reusable presentation assets. Desired: Allow a Super Agent to generate a slide deck from a prompt or source content, apply guided instructions such as company branding and formatting standards, and then save the output directly into Docs as an editable deck. The workflow should also support exporting that final deck into standard presentation formats, including: PPT PDF Business Justification: For enterprise teams, slide creation is rarely just about drafting content. It also requires brand consistency, editability, and distribution readiness. Acceptance Criteria: A Super Agent can generate a slide deck from a prompt, task, or source document Admins can provide instructions that influence branding, tone, and formatting The generated deck can be saved into Docs as an editable asset End users can continue editing the deck after generation The deck can be exported to PPT The deck can be exported to PDF The workflow is reliable enough to support repeatable enterprise use cases

Shared Documents, Sorting Documents based on Name, Ascending and Descending

Like PowerPoint or Google Slides

Make a feature where very important documents can have an added layer of protection from accidental deletion and have to go through an additional process to remove the delete protection before they could go to trash.

As a user, I would like to create a database within a page in docs (like in Notion) so that I can be more flexible with how I want my documents to appear and function.

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!

It looks like tables in docs have been slightly improved - https://clickup.canny.io/feature-requests/p/improve-tables-in-docs-big-time . However, still big improvements are needed: * Background color * Header formatting * More column width control * Cell merging * Center align tables * They still look ugly * ... I could go on and on At the very least implement something like Typora has - more control, more formatting options and rendering is quite good for markdown tables.