Feature Requests

Please search first before posting to help others find and vote for your idea!
Misleading UI in Sharing & Permissions Dialog Caused Unintended Billing for 6 Paid Seats (~$1,500 USD)
Feedback: Misleading UI in Sharing & Permissions Dialog Caused Unintended Billing for 6 Paid Seats (~$1,500 USD) Summary: When inviting users via the "Sharing & Permissions" dialog on a List, the "Default permission: View only" setting does not invite users as "Limited Member View Only" (a free role). Instead, it invites them as "Limited Members" (a paid role) with View Only permissions scoped to that specific List. There is no warning that this action will add paid seats and trigger billing. This distinction is not made clear anywhere in the dialog, and even ClickUp's own AI assistant (Brain) was unable to correctly distinguish between the two, giving the user incorrect guidance twice. Timeline of Events: User's goal: Invite 6 colleagues to view project data in a ClickUp Space without incurring additional charges, using the "Limited Member View Only" (free) role. Brain's initial guidance (incorrect): ClickUp Brain advised the user to right-click a List, open the "Sharing & Permissions" dialog, and invite users with "View Only" permission. Brain stated this would result in free, view-only access. User followed the guidance: The user opened the "Share this List" dialog on "All Task List 01," set "Default permission" to "View only," and invited 6 people. Result: All 6 users were registered as "Limited Members" (paid role), not "Limited Members View Only" (free role). The user's credit card was charged approximately $1,500 USD (6 paid seats) with no confirmation prompt or billing warning before the charge. Brain's second response (also partially incorrect): When the user reported the issue, Brain apologized and suggested changing each user's permission to "View Only" in the People settings, claiming this would convert them back to the free "Limited Member View Only" role. The user correctly identified that this advice was also likely wrong: the "View Only" permission in the sharing dialog controls location-level access, not the workspace-level user role. User's own analysis (correct): The user pointed out that "Permission: View Only" in the Sharing & Permissions dialog sets the access level for that specific location only. It does not determine or change the user's workspace role. To be invited as "Limited Member View Only" (free), the role must be explicitly selected elsewhere, likely in the People/Manage People settings, not through the sharing dialog. Core Issues: No distinction in the UI: The "Share this List" dialog offers a "View only" permission option but does not indicate that this is a location-scoped permission, not a role assignment. There is no mention of "Limited Member" vs. "Limited Member View Only" anywhere in this dialog. No billing warning: Inviting users through this dialog silently adds paid "Limited Member" seats. There is no confirmation step, no cost estimate, and no notice that the user's payment method will be charged. Even ClickUp Brain was confused: ClickUp's own AI assistant could not correctly distinguish between the "View Only" permission level (location-scoped) and the "Limited Member View Only" user role (workspace-scoped, free). Brain gave incorrect guidance twice, demonstrating that the naming and UX are genuinely confusing, not just to new users, but to the AI trained on ClickUp's own documentation. Recommendations: Add a billing confirmation step when inviting users through Sharing & Permissions that would result in new paid seats. Display the cost before the invitation is sent. Clarify role vs. permission in the sharing dialog. Either allow explicit role selection (Limited Member vs. Limited Member View Only) in the dialog, or display a clear label showing which role the invited user will receive. Rename or differentiate more clearly between "View Only" as a permission level and "Limited Member View Only" as a user role. The current naming is a trap. Update Brain's training data to accurately reflect the distinction between location-level permissions and workspace-level user roles, so the AI does not repeat this mistake. User context: New ClickUp customer (approximately 1 week), university research infrastructure manager (Osaka University, EPOCH project), migrating from Zoho. This experience has significantly undermined trust in both the platform's billing transparency and the AI assistant's reliability.
0
·
Sharing, Permissions,…
Load More
→