Task Settings
Task Settings control how tasks behave across your workspace: when due-date reminders go out, whether a task must belong to a project, what status a new task starts in, the taskboard's default length, and which parts of a task your clients are allowed to see.
These are workspace-wide defaults. Changing them affects every project's tasks, not just one.
Who can use it
Task Settings sit inside the Settings area, so you need an account with access to workspace settings — typically an admin role. Access is governed by role permissions, so if the page isn't visible, check the role's permissions first.
How to Access
- Open Settings from the sidebar.
- In the Organization list, select Task Settings.
Direct path: /account/settings/task-settings
The Settings hub itself lives at /account/settings and opens on Company Settings, so you may land there first before picking Task Settings from the list.
Due date reminders
Task Settings let you send reminders relative to a task's due date. You can send a reminder:
- Before the due date
- On the due date
- After the due date
These three are separate options, so you can run an early nudge, a day-of reminder, and a follow-up for overdue work — or only the ones you want. A task needs a due date for any of these to apply.
Is project required
The Is project required toggle (Yes / No) decides whether every task must belong to a project.
- Yes — a project must be selected when creating a task. Use this when you want all task activity to roll up under a project for reporting.
- No — tasks can exist on their own, without a parent project. Useful for standalone or internal to-dos that don't belong to client work.
Default status
New tasks start in the Incomplete status by default. Task status values are Incomplete, Under Review, and Complete.
So if you see a freshly created task sitting in Incomplete, that is the configured default rather than an error.
Taskboard Default Length
Taskboard Default Length is set to 10. This is the default number of items the taskboard uses when it loads.
If the board shows fewer tasks than you expect, this is the setting behind it.
Client visibility toggles
You can independently toggle which parts of a task are visible to clients. Each of the following sections has its own on/off control:
| Section | Section | Section |
|---|---|---|
| Task category | Due Date | Label |
| Priority | Comment | Timesheet |
| Hours Logged | Project | Assigned To |
| Assigned By | Make Private | Add File |
| Notes | Custom Fields | Start Date |
| Description | Status | Time estimate |
| Sub Task | History | Copy Task Link |
Turning a section off hides it from the client view of the task while leaving it intact for internal users. This is how you keep internal-only details — for example logged hours, timesheets, or task history — out of the client portal without changing how your team works.
Limitations
There are no separate client-facing status labels. Clients see exactly the same status values as your internal team. You cannot map an internal status to a different, simplified label for the client portal.
Workaround: your only lever here is the Status client-visibility toggle above — turn Status off entirely so clients don't see it, and communicate progress through comments or a client-visible label instead. If you need genuinely different client-side status wording, that is a feature request rather than a configuration change.
Reminders depend on a due date. A task with no due date is outside the before/on/after reminder logic entirely, so it will never trigger one.
Settings are workspace-wide. Default status, Taskboard Default Length, the project-required rule, and the client-visibility toggles apply across all projects. There is no per-project override in this screen.
Troubleshooting
Clients are seeing information I expected to be hidden. Check the client-visibility toggle for that specific section in Task Settings. Each section is controlled independently, so hiding Timesheet does not hide Hours Logged — you have to switch off each one you want concealed.
A client is confused by our internal status names. That is expected behaviour, not a misconfiguration: statuses are shared between internal and client views, and the values are the fixed set Incomplete / Under Review / Complete. Your option is to hide Status from the client view using its toggle and communicate progress another way.
Someone created a task with no project attached. The Is project required toggle is set to No. Switch it to Yes to force a project selection on every new task going forward.
New tasks aren't starting in the status I expect. The default status for a new task is Incomplete. If your workflow assumes a different starting point, adjust the task's status after creation or align your board's first column with Incomplete.
Only 10 tasks show on the board. That is the Taskboard Default Length, which ships as 10. Raise the value in Task Settings if you want the board to load more.
Related Articles
- Project Settings — project-level defaults that pair with these task rules
- Time Log Settings — timesheet and time-tracking configuration referenced by the Timesheet and Hours Logged toggles
- Taskboard — the board these settings drive
- Creating Tasks — where the project-required and default-status rules take effect
- Task Reminders — reminders at the individual task level
- Custom Fields — the custom fields covered by the client-visibility toggle
- Module Settings — turn the Tasks module on or off per user type