Feature Requests

ClickUp currently has no way to toggle a channel from public to private and automatically keep all existing followers as members. There's no programmatic or UI option to read the follower list, flip the privacy switch, and re-add everyone in one go.

Currently, Chat notifications and Inbox/task notifications use the same notification sound, making it difficult to distinguish between urgent communication and routine project updates without stopping work to check ClickUp. As organizations increasingly use ClickUp as both a project management platform and a communication tool, not all notifications carry the same level of urgency. A direct chat message from a colleague often requires immediate attention, while a task assignment, comment, status update, or reminder may not. Providing distinct notification sounds for different notification types would help users prioritize their attention more effectively and reduce unnecessary context switching. Example: * Chat Message → Sound A * Inbox/Task Assignment → Sound B * Mention/Direct Tag → Sound C * SyncUp Invitation → Sound D Benefits: * Helps users quickly determine notification urgency without opening ClickUp * Reduces interruption and context switching * Improves responsiveness to direct communication * Decreases notification fatigue * Enhances productivity and focus * Creates a more intuitive experience for teams using ClickUp as their primary communication platform Ideal Functionality: * Different default sounds for Chat, Inbox, Mentions, and Meetings/SyncUps * Ability for users to customize notification sounds by notification type * Workspace-level defaults with user-level overrides * Consistent behavior across desktop and mobile applications Today, a direct message from a teammate and a task due weeks from now generate the same notification sound, making it impossible to understand the importance or urgency of a notification without manually checking it. Distinct notification sounds would provide valuable context and help users manage their attention more effectively throughout the workday.

It would be extremely valuable for ClickUp Chat to display real-time status indicators next to users' names, similar to Slack. Today, users often have no visibility into whether a teammate is currently in a meeting, participating in a SyncUp, focused on deep work, out of office, or otherwise unavailable. This can lead to unnecessary interruptions, delayed responses, duplicate follow-ups, and reduced collaboration efficiency. Adding presence and status indicators directly within Chat would provide immediate context about a teammate's availability and help teams communicate more effectively. Examples of Status Indicators:** * In Meeting * In SyncUp * Focus Time / Do Not Disturb * At Lunch * Out of Office * Away * Available * Offline Benefits: * Reduces interruptions during meetings and focused work * Helps set expectations for response times * Improves collaboration across distributed and remote teams * Increases visibility into team availability without requiring additional messages * Reduces the need to switch between ClickUp and external communication tools * Supports ClickUp's vision as a centralized work and communication platform Ideally, status indicators could be updated automatically based on ClickUp Calendar events, SyncUps, scheduled focus time, or manually by users when desired. The more context users have about team availability directly within Chat, the more efficient and effective communication becomes.

Currently, chat channels that are created accidentally, created for testing purposes, or no longer needed cannot be permanently deleted. This creates unnecessary clutter within the workspace and makes it more difficult for users to navigate and locate active, relevant conversations. It would be extremely valuable to provide Workspace Owners and Administrators with the ability to permanently delete chat channels when appropriate. Benefits: * Reduces workspace clutter and improves organization * Allows administrators to clean up channels created by mistake * Improves user experience and channel discoverability * Prevents confusion caused by outdated or unused channels * Supports better workspace governance and administration Ideally, this functionality would include appropriate permission controls so only Workspace Owners and Administrators (or designated roles) can delete channels, helping prevent accidental data loss while maintaining administrative flexibility. As organizations scale and adoption of ClickUp Chat increases, having the ability to properly manage and remove unnecessary channels becomes increasingly important.

In chat UI at desktop we can see from which space the chat is by a fadded name at the right. We should have some likewise indication in the mobile too.

Sometimes people start threads in unrelated channels. I would be great to move a chat or a thread from one channel to another one; or at the very least, to copy the thread from one channel to another and then have the option to grey out, relate or deactivate the thread that should no longer be added to. Another use case is scope creep. When one thread suddenly moves from the topic at hand to a whole other conversation that should really belong in a different channel altogether.

Currently, ClickUp does not allow users to remove themselves from a direct message conversation. Would be great to be able to remove someone who has been added to a chat by mistake.

It would be great if there was an automated message when a new person was added/joined an existing channel/chat. As well as a note that signalled when chat messages had been edited.

Add a pen to highlight anything on shared screen of the other person so that we can guide them with tasks.

Hi ClickUp Support, I'm using ClickUp Desktop on Linux (AppImage) and spellcheck has stopped working in the chat editor. It used to highlight misspelled words, but it no longer does. Environment: OS: Ubuntu/Linux ClickUp Desktop (AppImage) Electron 41.2.0 / Chrome 146.x What's happening: Spellcheck is enabled in system preferences (~/.config/ClickUp/preferences.json has "dictionaries": ["en-US", "ru-RU"]), and the Electron session confirms it is active (spellCheckerEnabled: true, languages: ["en-US", "ru-RU"]). However, right-clicking on a clearly misspelled word always shows an empty misspelledWord field with no suggestions. Root cause I identified: The ProseMirror-based chat editor intercepts all keyboard input via beforeinput event and calls preventDefault() before inserting text directly into the DOM. Because of this, Chrome's input pipeline never registers the keystrokes as "user-typed text" - which is a prerequisite for the native spellchecker to run. As a result, spellcheck is silently skipped regardless of session or element-level configuration. This is a known incompatibility between ProseMirror's input handling and Chromium's spellcheck mechanism. Request: Please integrate spellcheck at the ProseMirror/editor level directly - either by using a JS-based spell checking library (e.g. nspell, typo.js) or by invoking Electron's webContents.session.checkSpelling() on words after they are committed to the editor state, and surfacing corrections through the editor's own suggestion UI or context menu. This is a significant usability issue for non-English speakers who rely on spellcheck to write in multiple languages. Thank you.