Feature Requests

Please search first before posting to help others find and vote for your idea!
Support placeholder / non-licensed users in Org Chart without triggering invites
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.
2
·
People, Profiles, Pulse
Assign Hourly Rates to Team Members and Calculate Task Cost Based on Time Tracked or Logged Hours
Hi ClickUp Team, I'd love to request a feature that would be incredibly helpful for cost tracking and project budgeting within ClickUp. 🎯 The Problem: Currently, there's no built-in way to associate an hourly rate with individual team members and then automatically calculate task costs based on time tracked or manually logged hours. This gap creates friction when trying to manage budgets and track actual costs in real-time across tasks and projects. 💡 Proposed Solution: Hourly Rate Field per User: Add a new field where Workspace admins can assign an hourly rate to each team member. This can be either a global setting or project-specific override. Cost Calculation Functionality: Enable an automatic cost computation based on the hourly rate and time tracked (via ClickUp’s time tracking feature). Alternatively, allow this cost to also be computed when someone manually enters the number of hours in a field (e.g., a custom "Time Spent" field). Dynamic Cost Field: Introduce a new computed custom field called “Cost” (or allow a formula field) that multiplies the user’s hourly rate by their tracked or entered time. This field should update automatically based on changes to time or rate. 📊 Use Case Example: Jane has an hourly rate of $50. She logs 3 hours on Task A using the time tracker. The system automatically records a cost of $150 for that task. If she instead enters “3” into a “Manual Hours” field, the same cost gets computed dynamically. ✅ Benefits: Helps teams stay on top of project budgets. Useful for internal cost tracking, client billing, and reporting. Reduces the need for external spreadsheets or manual calculations. This would be a game-changer for project-based businesses, agencies, and consulting teams using ClickUp. Looking forward to your consideration! Best, Tarif
4
·
People, Profiles, Pulse
Load More