Problem:

When using Tasks in Multiple Lists to share tasks across different audiences (e.g., an internal engineering list and an external client-facing list), all Custom Fields from the task's Home List are visible when opening the task detail, regardless of which list the viewer is accessing it from. There is no way to hide specific fields per view or per list context.

This creates an information leak: internal fields like "Complexity," "Internal Cost," or "Engineering Notes" are fully visible to external stakeholders (clients, partners) who access the task from a client-facing list. The only workaround today is to not use multi-listing at all and duplicate tasks manually, which defeats the purpose of the feature.

Use case:

We are a managed services company that uses ClickUp to run projects. Our internal engineering team works from one Space with detailed operational fields. We share project progress with clients through separate lists in a client-facing Space. Multi-listing is the natural solution, but because we cannot control field visibility per context, we are forced to either expose internal data to clients or abandon multi-listing entirely.

Proposed solution:

Allow Workspace admins or view creators to configure which Custom Fields are visible in the task detail panel on a per-view or per-list basis. When a user opens a task from a specific list/view, only the fields enabled for that context should appear in the detail panel, not just in the column headers.

Impact:

Without this, Tasks in Multiple Lists loses its value for any organization that needs audience separation (internal vs. external, team A vs. team B). This is a common need for agencies, consultancies, and IT service providers who share project visibility with clients inside ClickUp.