Feature Requests

It would be wonderful if ClickUp had the option to select metadata from a People custom field when adding the field to an automation, dashboards, List Views, email, comment, etc. If I select a People custom field right now, it will enter in the user's display name. This is usually fine, but there is a lot of metadata associated with that particular user, like their email address, assigned manager, or ClickUp account creation date that would be helpful in other situations. For example, I have created a dashboard with a task view that shows a People custom field and some other data. I will export the task view to send to another co-worker who needs to upload the data into another software system to perform some work on the data. Right now, only the user's display name appears in the People custom field. It would be amazing if I could have a column that showed the display name of the People custom field and their email in another column.

Currently, Personal Time Off only supports "not working" states (sets capacity to 0, warns on task assignment). But many teams need to track where people are working from, not just whether they're off. Proposed solution: Add a "location-based" or "partial availability" time off type (e.g. Home Office, Remote) that: Shows up in the same Time Off card in Teams Hub so managers can see who's remote today Does NOT reduce capacity to zero (person is still working) Appears in Calendar, Workload, and Gantt views as a visual indicator Is visible to all team members, not just admins Why it matters: Hybrid teams need a single place to answer "who's in the office today?" The Time Off system is the natural home for this, but right now you're forced into workarounds (User Status, separate task lists) that fragment visibility.

Currently, the Verified Power User badge only displays on internal ClickUp profiles. There's no individual credential URL or integration (like Credly) that lets users prove their badge externally, such as on LinkedIn. The "Share on LinkedIn" flow drafts a post, but a post isn't a verifiable credential. It would be much more valuable if each badge recipient got a unique URL (e.g. clickup.com/verified/user/abc123 ) that confirms their status, which they could add to LinkedIn's Licenses & Certifications section. This would make the badge actually mean something outside of ClickUp and give users a reason to showcase it professionally.

ClickUp’s Org Chart depends on active ClickUp user records. That creates a gap for enterprise teams that need to represent full reporting structures, including people who should appear in the org hierarchy but should not receive workspace access yet — or ever. In practice, admins may need to: model leaders or employees before they are provisioned in ClickUp, preserve reporting lines for contractors, future hires, or external stakeholders, avoid sending an invite email the moment a user object is created, retain org-chart continuity after a user is deactivated or removed. Today, those use cases break down because adding someone to the user model is too tightly coupled to inviting them into the product, and deactivation/removal can disrupt the org chart. Desired: Admins should be able to create and maintain org-chart-only people records separately from product access. That means: - create a person/user record without immediately sending an invite, - trigger the first invite as a separate admin action when the person is actually ready for access, - allow non-licensed or placeholder records to appear in the Org Chart, - preserve historical and current reporting relationships even after a user is deactivated or deleted. This would align better with how enterprise systems handle identity vs. access. Platforms like Workday and Salesforce commonly separate a person’s presence in the system from whether they are currently licensed or activated for a given tool. Business Justification: For enterprise admins, the Org Chart is not just a collaboration view — it is an operational system of context for HR, managers, program owners, and change leads. When Org Chart visibility requires full product activation, teams run into several issues: Admin overhead: admins must create workaround records or prematurely provision users just to complete reporting structures. Poor change management: future hires, pending transfers, and preboarding scenarios cannot be represented cleanly. User experience risk: invite emails may be sent before the employee is ready, causing confusion and support tickets. Data continuity issues: deactivated users disappearing from the hierarchy can break downstream understanding of team structure. Scalability constraints: large enterprises need the org chart to reflect the business as it exists, not only the subset of people currently licensed in ClickUp. Separating identity representation from workspace access would make the Org Chart significantly more usable for enterprise deployment and reduce manual cleanup for admins. Acceptance Criteria: Admins can create a person record that appears in the Org Chart without sending an invitation email. Admins can manually trigger the first product invite later as a separate action. Non-active / non-licensed people records can be included in the Org Chart with a clearly identifiable status. Deactivated users do not break manager/direct-report relationships in the Org Chart. Deleted or archived records can be handled in a way that preserves org-chart integrity and historical structure. Admins can distinguish between org-chart visibility and workspace access state. Suggested Solutions: Add an “Org Chart only” user type Pros: cleanest enterprise model; easy for admins to understand. Cons: requires a new user lifecycle/state model. Separate “Create user record” from “Send invite” Pros: likely the fastest path; solves the immediate invite problem. Cons: may not fully solve deactivation/history use cases on its own. Preserve deactivated users as inactive nodes in the Org Chart Pros: protects structural continuity and historical reporting lines. Cons: still needs clear UX to avoid confusion with active users. My recommendation: combine #2 + #3 as the shortest path to value, with #1 as the longer-term enterprise-grade model.

Currently, subtasks do not inherit followers from the parent task. We need an option to have subtasks automatically add all parent task followers so that key stakeholders stay updated on all related work without needing to manually add them to every subtask. This would significantly improve cross-team visibility and streamline our communication workflows.

Would be great to have the birthday from a team member or even guest addressed in the profile so: the team could congratulate them clickup could send a bday message congratulating the person

Hello, ClickUp Team, I'm managing a large scale operation with multiple business units and dozens of users within the same Workspace. To scale our project management and maintain data governance, we urgently need a security/permission update in the format in which users interact with tasks. Currently, if a user has access to a List, they can view all the tasks within it. However, for the efficiency of our operation, we need granular permission controls based on Custom Fields or User Groups. The ideal scenario would be to configure permissions so that a specific user or team can view/access only those tasks that match an exact filter (for example: Tasks where the “Custom Field: Region” equals “X”, or Tasks belonging to your specific User Group). We were able to do this with high performance on CRM platforms like HubSpot, where access to properties and views can be restricted by team. In ClickUp, managing this today requires us to create dozens of separate lists or spaces, which breaks our ability to have a unified architecture and impacts our dashboards. Allowing administrators to force “Filtered Views” or restrict task visibility based on Custom Field values would be an absolute game-changer for managing large companies and multi-clinic networks. Is this granularity of permissions in your product roadmap for upcoming updates?

It would be nice to be able to set a profile picture for a user if I am the admin of a workspace.

The People's tab is the only place we are able to view certain details like 2FA status, Pending invite status . And we should manually export that to get the details in a usable format. We would like to have a scheduled report export, such that we can build workflow automations based off of that data. There are no API endpoints to retrieve 2FA status or the Pending invite status.