Table of Contents

Tasks & Task Templates: Overview

Jennifer Trower Updated by Jennifer Trower

Read Time: 4 mins

This article outlines the updated structure and behavior of the Task feature in Sonar, including new functionality such as centralized task management and enhanced task group logic. It is intended to help users understand where tasks are managed, how they function, and the roles required to interact with them. Whether you're assigning a task to a user, building out templates for repeatable workflows, or managing visibility within user profiles, this guide explains how the system works and what steps you need to take.

Permissions

Before getting started with the feature, your user roles will need to be adjusted to account for the permissions required to use the Task feature.

If you're a Super Admin, you already have full access, and no changes are needed. To learn more, see the Roles and Permissions article.
  1. Tasks (Main Menu): Access to Centralized Task Management.
  2. Task Groups (Settings → Tasks): Manage task groups and member associations.
  3. Task Templates (Settings → Tasks): Create and manage task templates.

Where Tasks Appear

Tasks can be created on container entities such as Accounts, Tickets, Jobs, Network Sites, Trackable Inventory Items, and Serviceable Addresses. Once created, tasks appear in three places:

  1. On the container entity’s own task section,
  2. In the Centralized Task Management page accessible via the main menu,
  3. In each user’s profile under the Tasks tab, depending on assignment rules.

Using Task Templates

Task Templates allow for repeatable task creation and can define default assignments or groups. Templates are managed via Settings → Tasks → Task Templates and follow all entity mapping rules to ensure compatibility.

When a template is applied, the system validates whether the required custom fields are valid for the selected entity type. Invalid options are hidden during selection to avoid errors.

Managing Task Groups

Task Groups can be managed under Settings → Tasks → Task Groups. Groups must include at least one user to appear in profile views.

Groups can be enabled or disabled but cannot be deleted once they’ve been used. There are no dependencies when assigning a user to a task or tagging a task with a group—these two options operate independently.

Creating and Managing Tasks

When creating a task, the entity must be selected first, followed by the assignee. You can complete this by going directly to the assignee (account, job, serviceable address, etc.) and creating the task from the Overview management tab or by going to Tasks within the main menu.

  1. On any assignee
  1. Tasks within the main menu.

Tasks can be assigned to a user, a task group, or both—these fields are independent, and the drop downs are not restricted by the other field’s selection.

Optional fields include a due date (which appears red if the task is overdue) and completion requirements. Completion requirements can include uploading a file or image or entering a custom field value. Depending on the "Entity" selected will depend on which "Completion Requirements" are available for selection.

If a completion requirement exists, the task cannot be marked incomplete once it has been completed.

Users can also reorder tasks on an entity using the “Change Task Order” feature.

Centralized Task Management

Centralized Task Management is a new area under the main menu that offers two main views: Incomplete and Complete. Users can filter by various fields and reassign or claim tasks directly from this view.

Incomplete tasks support saved filters, including “Assigned Tasks,” “Unassigned Tasks in Task Group,” and “Unassigned Tasks without Task Groups.”

Viewing Tasks in User Profiles

Within the User Profile, the Tasks tab offers three views: My Incomplete Tasks, My Completed Tasks, and Unassigned Tasks (for the groups the user belongs to). Tasks appear in a user’s profile if they are directly assigned or belong to a group the user is in. Users can edit, complete, or reassign tasks from this view if permissions allow. The default filter is set to show only the logged-in user’s tasks and unassigned tasks from their groups.

Completion Requirements and Custom Fields

Completion requirements can include custom fields from related entities. For example, a Job task can require a field value from the associated Account. The system enforces a list of approved entity relationships to ensure valid mappings. Unsupported combinations are filtered out of the UI to prevent errors. Templates and task requirements will only display valid fields and entities based on these predefined mappings.

Task Template Containing Task with this Completion Requirement Type

Entity

None

File

Image

Account Custom Field

Address Custom Field

Job Custom Field

Network Site Custom Field

Ticket Custom Field

Service Metadata

Account

✅ Yes

✅ Yes

✅ Yes

✅ Yes

❌ No

❌ No

❌ No

❌ No

✅ Yes

Address

✅ Yes

✅ Yes

✅ Yes

✅ Yes

✅ Yes

❌ No

❌ No

❌ No

✅ Yes

Inventory Item

✅ Yes

✅ Yes

✅ Yes

❌ No

❌ No

❌ No

❌ No

❌ No

❌ No

Job

✅ Yes

✅ Yes

✅ Yes

✅ Yes

✅ Yes

✅ Yes

❌ No

❌ No

✅ Yes

Network Site

✅ Yes

✅ Yes

✅ Yes

❌ No

❌ No

❌ No

✅ Yes

❌ No

❌ No

Ticket

✅ Yes

✅ Yes

✅ Yes

✅ Yes

✅ Yes

❌ No

❌ No

✅ Yes

✅ Yes

How did we do?

Specify Account ID upon Creation

Using Sonar's FCC Broadband Label Generation Tool

Contact