Feature Requests

Please search first before posting to help others find and vote for your idea!
Keeping Team Projects Organized from Start to Finish
Planning a successful project involves more than creating a list of things to do. For example, bubble tea catering https://bubbleteacatering.uk/ can involve several tasks that need to be managed together. From choosing flavors to arranging delivery, each step needs clear planning and communication. The same idea applies to teams managing projects in a shared workspace. Breaking a large project into smaller tasks makes the workload easier to understand. Each task can have a clear owner and a deadline. This helps everyone know what needs to be completed and when. A shared task list also makes it easier to follow progress without asking for constant updates. When plans change, team members can update tasks so everyone stays informed. Comments can keep important discussions connected to the work they relate to. Documents are useful for storing instructions, meeting notes, and project details. Keeping these resources organized reduces the time spent searching for information. Different views can help people understand the same project in different ways. A list may work well for daily tasks, while a calendar can help with scheduling. For projects with many steps, dependencies show which tasks need to happen first. This can prevent teams from starting work before the necessary preparations are complete. Regular check-ins also help identify delays before they become bigger problems. Clear responsibilities make it easier to see where support may be needed. It is equally important to leave room for unexpected changes. A practical workflow should help people stay organized without adding unnecessary complexity. Teams can review their process and adjust it as they learn what works best. Small improvements in planning can make collaboration smoother over time. When information is easy to find, people can spend more time completing meaningful work. In the end, good project management comes down to clear tasks, shared information, and consistent communication.
0
·
Automations
Workspace-level logging and export of all Super Agent conversations, including DMs
PROBLEM Workspace owners can't see or export what users ask Super Agents in direct messages, or what the agents reply. Super Agent Activity only shows run metadata (trigger, status, tools used). Audit Logs don't include transcripts. So a growing share of AI-driven work has no audit trail. For regulated businesses this blocks adoption. We run a licensed online operation under ISO 27001 and GDPR, with a regulator overseeing us. We have to show what our AI agents were asked, what they did, and what data they touched. Right now we can't, so we have to restrict Super Agent use. REQUESTED CAPABILITY Full transcript logging: every prompt, response, tool call and tool output, across DMs, channels, tasks and automations, with timestamps, user and agent IDs. Owner/admin access: a central view where owners or a delegated role can search and filter by user, agent, date range and keyword. Export: CSV/JSON export, plus API access or a SIEM/webhook stream so logs can go to our own retention system. Retention controls: configurable retention periods and legal hold, plus deletion of a single user's data for GDPR erasure requests. Tamper evidence: logs can't be edited or deleted by the end users who created them. User notice: an optional banner telling users their agent conversations are logged, to support transparency obligations. WHY IT MATTERS It closes the main governance gap that stops regulated companies (finance, gambling, healthcare, legal) from rolling out Super Agents widely. It supports ISO 27001 logging and monitoring controls, GDPR access and erasure requests, and internal AI governance. Competing enterprise AI tools already offer conversation audit and export, so this matters for enterprise deals. PRIORITY FOR US: High. It's a precondition for wider Super Agent rollout across our Workspace.
0
·
ClickUp AI
Knowledge Spaces – Notion-Style Intranet, Native Databases & Granular Permissions
Feature Request: Knowledge Spaces – Notion-Style Intranet, Native Databases & Granular Permissions Overview ClickUp’s vision of “One app to replace them all” is compelling. However, while ClickUp is excellent at task and project management, it still lacks the flexibility of Notion when it comes to building an internal company intranet, managing structured knowledge, and organizing databases independently of tasks. I would love to see ClickUp introduce Knowledge Spaces, a dedicated environment for company knowledge management that exists independently of the current task-based hierarchy. Dedicated Knowledge Spaces Introduce a new type of Space specifically designed for knowledge management rather than task management. Key capabilities: * Create nested pages and subpages, similar to Notion. * Build company intranets, department portals, internal wikis, and knowledge bases. * Organize content through a flexible sidebar hierarchy. * Embed databases, documents, dashboards, and other content directly within pages. * Link relevant pages and database records to ClickUp tasks when needed, without treating everything as a task. Native Databases (Independent of Tasks) Please introduce Notion-style databases as first-class objects within Knowledge Spaces. Features should include: * Custom properties and field types. * Table, Board, Calendar, Gallery, and List views. * Database relationships, rollups, and formulas. * Linked database views that can be embedded across multiple pages. * Filtering, sorting, grouping, and reusable templates. * Database records that can contain full pages of content. Importantly, database records should not need to be ClickUp tasks. For example, companies should be able to manage policies, contracts, employee skills, company assets, meeting records, and internal knowledge without creating artificial tasks. Granular, Notion-Style Permissions This is particularly important for using ClickUp as an enterprise intranet. I would like to see flexible permission management at multiple levels: * Knowledge Space level * Folder and page level * Database level * Individual database record level, if feasible Ideally, permissions would support: * Different roles such as Full Access, Can Edit, Can Comment, and Can View. * Permissions assigned to individual users and groups. * Permission inheritance from parent pages, with the ability to configure exceptions. * Private pages and databases accessible only to explicitly authorized users. * Organization-wide knowledge areas that employees can read but only designated owners can edit. * Clear visibility into who has access to each page or database. * Search and AI features that strictly respect each user’s access permissions. For example, a company could maintain an open internal knowledge base accessible to all employees, while restricting HR, legal, M&A, and management information to specific authorized groups. Linked database views must also respect the permissions of the underlying database and records. Integration With Existing ClickUp Features Knowledge Spaces should integrate seamlessly with ClickUp Tasks, Docs, Dashboards, Automations, and AI. Ideally: * Tasks could link to knowledge pages or database records. * AI could search and summarize authorized knowledge across the organization. * Automations could operate on database records. * Knowledge could be reused across departments without unnecessary duplication. Why This Matters Many organizations currently need both ClickUp and Notion because the two products serve different purposes: ClickUp = Task and project management Notion = Knowledge management, databases, and company intranet If ClickUp introduced Knowledge Spaces with native databases and granular permissions, organizations could genuinely consolidate both functions into a single platform. I am not suggesting that ClickUp replace its existing task management model. Instead, I believe task management and knowledge management should become two complementary, first-class capabilities within the same workspace. This would be a major step toward making “One app to replace them all” a reality.
0
·
Docs
Load More
→