ClickUp Form Settings: Home, Spaces, Sharing, and Task Routing

What ClickUp Form settings control

ClickUp Form settings connect an external or internal request to a task-based workflow. Depending on the form and workspace configuration, the settings can control access, form collaboration, task creation, field mapping, and the default destination for new tasks.

These choices should be treated as one system rather than isolated options. If a form is open to a broad audience but creates tasks in a restricted List, submissions may be difficult for the delivery team to process. If the destination List is correct but the form does not capture enough information, staff will need to repair every task manually.

How to open Form settings from Home

The Home Sidebar is useful when you want to find and manage forms without first navigating through a specific Space, Folder, or List.

1. Open Home from the left Sidebar.
2. Find the Forms area or the form you want to manage.
3. Select the relevant form.
4. Open the form’s options menu or settings control.
5. Choose Form settings.

From there, review the settings before changing them. In particular, confirm that the form is still connected to the intended operational process and that its destination has not become obsolete.

How to open Form settings from Spaces

Use the Spaces Sidebar when the form is managed alongside the work it creates. This route can make the relationship between the form, its target List, and the team responsible for the resulting tasks easier to understand.

1. Open Spaces in the left navigation.
2. Select the relevant Space.
3. Navigate through the Folder or List where the form is located, if required.
4. Open the Forms area or Forms view.
5. Select the form and open its options menu.
6. Choose Form settings.

The exact labels and navigation may vary by ClickUp workspace configuration or product version. If a form is not visible, check the location, access permissions, and whether you are viewing the correct Space or List.

Configure access and collaboration before launch

Access settings answer two different questions: who can submit the form, and who can change the form itself. Keep those responsibilities separate.

Decide who can submit

First decide whether the form is intended for internal requests, known external contacts, or anyone who receives a link. A public link may reduce friction for broad intake, while workspace-only access may be more appropriate for requests containing internal information.

Do not choose the broadest access setting simply because it is convenient. Define the data being collected and the people who need to review it. The right setting is the one that allows the intended respondents to provide information without exposing more of the workflow than necessary.

Decide who can edit

Form editing should normally be limited to the people responsible for maintaining the intake process. A person who submits a request does not necessarily need permission to change the questions, routing, or destination.

Make ownership visible by naming a responsible role or team. Review the form when the underlying process changes, when the destination List changes, or when submissions begin arriving with incomplete or inconsistent information.

Set how form responses become tasks

The task created from a submission should contain the minimum information needed for the next person to make a decision or begin work. Configure the form around that requirement rather than collecting every detail that might be useful someday.

Map the task title and description

Choose a form question that produces a meaningful task title. A title such as “New request” provides little value when a team is scanning a List. A title that identifies the request type, subject, or affected customer is easier to triage, provided the respondent can supply it reliably.

Use a long-text field for context that belongs in the task description. Explain to respondents what a useful answer contains, such as the desired outcome, relevant background, or a link to supporting material.

Map structured fields deliberately

Use consistent fields for information that will later support filtering, grouping, assignment, or reporting. Examples may include request type, urgency, department, service area, or due-date information.

Do not create a separate custom field for every variation of the same concept. Standardized values are more useful than free-text answers when a team needs to compare requests or report on demand.

Set initial status, priority, and ownership

Initial values should represent the real starting state of the work. For example, a submitted request may need a review or triage status before it becomes ready for delivery. Assign a default owner only when that person or team genuinely owns the next step. An automatic assignment that no one monitors creates false accountability.

Choose the default List for new submissions

The destination List is one of the most important Form settings because it determines where new work enters ClickUp. Select the Space, Folder, and List that match the operating process, then test the result with a real submission.

1. Open Form settings from Home or Spaces.
2. Find the destination, default List, or equivalent location setting.
3. Open the location picker.
4. Select the intended Space, Folder, and List.
5. Save or apply the change.

Changing the default destination generally affects new submissions. It does not automatically redefine the business meaning of tasks that were created previously. Existing tasks remain part of their original history unless someone moves them deliberately.

Avoid creating separate Lists only to make forms appear organized. More locations can make ownership and reporting less clear. The destination should be determined by where the first meaningful business decision occurs.

Use a simple setup sequence

When configuring a new form or reviewing an existing one, use this sequence to avoid treating individual settings as disconnected preferences.

Test the workflow, not just the form

A successful test is more than checking that a confirmation appears. It verifies that the receiving team can act on the resulting task without reconstructing the request.

Use at least one normal submission and one incomplete or unusual submission. The second test exposes whether the form gives respondents enough guidance and whether the team has a defined response to poor-quality intake.

Example: a service request form

Consider a hypothetical internal service request form. The process owner wants employees to request help, while an operations coordinator reviews the request before assigning it to a specialist.

The form might collect the request type, desired outcome, urgency, affected system, and supporting details. New tasks could enter a central triage List with a review status and the coordinator as the initial owner. Specialist assignment would happen only after the coordinator confirms that the request is complete and correctly categorized.

This design is more reliable than assigning every submission directly to a specialist. It separates intake from delivery and gives the team a visible place to correct incomplete requests.

ConsultEvoClickUp ConsultingSupport for ClickUp workspace architecture, workflows, dashboards, automation, and integrations.→

Operational rules for maintaining ClickUp Forms

Review a form when the team changes its intake process, when a List is renamed or replaced, or when reports show that submissions are being reclassified manually. A high volume of corrections is usually a design signal, not just a user problem.

Keep form questions aligned with business states. “Submitted,” “Needs review,” and “Ready for delivery” describe states of work. “Form completed” describes an activity. Confusing the two can make statuses and reporting less useful.

Document the form’s purpose, owner, destination List, and review cadence in a location your team can maintain. If the workflow later requires automation or connections to other systems, the decision logic should be clear before tools are added. More automation cannot compensate for an ambiguous intake process.

For broader systems work, the same process-first approach applies to systems, CRM, automation, and AI implementation services. In a ClickUp-specific context, the goal is a workspace that reflects real ownership and business states rather than a collection of disconnected views.

ConsultEvo PortfolioInternational Talent Recruitment and ClickUp Hiring WorkflowA relevant example of a tailored ClickUp workflow supporting a recruitment process.→