Feature Requests

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.

It would be very helpful to have a feature that allows toggle lists to be set as either expanded or collapsed by default. Currently, when content is hidden inside a collapsed toggle, the document’s search function cannot locate words or sentences within it. This forces us to manually expand each toggle one by one, which is time-consuming and inefficient. Having the option to control the default state of toggle lists would greatly improve usability and search efficiency

It is currently not possible to copy and paste from tables (in Docs) into other areas of ClickUp, or other applications. This is a major limiting factor in using Tables in Docs. We really need the ability to copy and paste from Doc Tables to anywhere in ClickUp or other applications.

Add native support for uploading and rendering OpenAPI specifications (YAML/JSON) directly within ClickUp Docs, similar to the Swagger Editor experience. Problem Statement: Currently, teams working with APIs need to maintain their API documentation separately from their project documentation in ClickUp. This creates friction as developers must switch between multiple tools to: View API documentation: Test API endpoints Keep documentation in sync with project tasks and workflows Proposed Solution: Enable users to upload or embed OpenAPI specification files (YAML or JSON format) into ClickUp Docs, which would then be automatically rendered as an interactive API documentation interface - similar to the right-hand preview panel in https://editor.swagger.io Key Features: File Upload/Embed: Allow users to upload .yaml, .yml, or .json OpenAPI specification files directly into a Doc Interactive Rendering: Automatically render the spec using a Swagger UI-like interface showing: -All API endpoints organized by tags/categories Request/response schemas Example payloads Authentication requirements Live Preview: Real-time rendering as the spec file is updated Version Control: Track changes to API specs over time (similar to Doc version history) User Flow: User creates or opens a ClickUp Doc User clicks "Add OpenAPI Spec" or uses a slash command like /openapi User either: Uploads a local .yaml or .json file Pastes the spec content directly Links to an external spec file 4.ClickUp automatically renders the specification as interactive API documentation The rendered documentation is embedded inline within the Doc, maintaining the context of surrounding content Benefits: Centralized Documentation: Keep API docs alongside project planning, task management, and team collaboration Developer Experience: Developers can reference and test APIs without leaving ClickUp Single Source of Truth: Reduce documentation drift by housing everything in one platform Better Collaboration: Non-technical stakeholders can view API capabilities in a user-friendly format Workflow Integration: Link API endpoints directly to tasks, sprints, or feature requests Similar Implementations: Swagger Editor ( https://editor.swagger.io ) - Split view with YAML/JSON on left, rendered docs on right Use Cases: Product Teams: Document internal/external APIs alongside product requirements Engineering Teams: Maintain API contracts within sprint documentation Partner Integration: Share API documentation with external partners in shared Workspaces API-First Development: Design APIs in ClickUp before implementation Technical Considerations: Support OpenAPI 3.0+ specification standard Render using existing open-source libraries (Swagger UI, Redoc, or similar) Handle large specification files efficiently Optional: Allow customization of rendering theme to match ClickUp aesthetics

GitLab/Github wikis give the possibility to render plantuml/mermaidjs diagrams. It would be awesome to have the same feature.

It can happen that for example marketing terminology changes. Currently you cannot search and replace in clickup docs. So this would be useful.

Currently, my Docs card shows each page of a document as a separate document. This adds a lot of clutter to my card. I would like to be able to make each document only appear once in the Docs card.

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.

Adding an image to a doc automatically gets formatted with a border around it. I would like to be able to remove the borders around images. It doesn't matter how it gets done. It can be a setting for all docs, a doc or per added image. Just make it possible to remove the borders and let me decide If there's a need for it. Best regards