In the new UI we have added a dedicated filter for ConnectWise boards or Autotask queues.

For ConnectWise ticket and project views:

For Autotask ticket views:

ConnectWise board and Autotask queue are common choices for filtering tickets, and using this field for filtering is easier than setting up the equivalent filter in the query builder.

Furthermore, for ConnectWise ticket views, the selected boards are used to filter the list of statuses on the Workflows tab, making it much easier to assign statuses to workflow stages. This can reduce the number of statuses in the list from hundreds to just 10 or 20.

For what it's worth, the ConnectWise board selection above is equivalent to this query builder filter:

Join us on January 29 to hear what we've been up to the last few months, including:

• All‑new Capacity Planning module: instantly see who’s available now and how much work you can take on next
• Refreshed UI: faster navigation with less friction so your team gets more done
• 2026 Roadmap: hear what’s coming next to help you stay ahead of project overload and workload bottlenecks

This isn’t just another feature overview... it’s your chance to see what TopLeft can really do for MSP workflows, both operationally and strategically, and to ask questions live with our product team.
 
Date: January 29, 2026

Time: 1pm PST / 4pm EST
Length: 1 hour
 
Reserve your seat: Product Update & Roadmap Webinar
 
Can’t make it live? Register anyway and we’ll send you the recording.

We're excited to show off more of the new version of TopLeft! If you want to use this new UI in TopLeft, please email help@topleft.team to request access.

Some of the improvements in the new UI are most applicable to administrators and managers who set up boards, and other improvements are for everyone who uses boards and Gantt charts.

Improvements for Managing Boards/Views

We completely rebuilt how boards and Gantt charts are configured. The new way is easier and more flexible than the old way.

To take advantage of the new UI, you need to make a new view. Old boards still show up in the old UI. We will be introducing migration tools in February.

Flexible query builder

To choose which tickets appear on a board, views are set up using a flexible query builder. Compared to the old version, this lets you make use of boolean operators (and/or/not), searching by name (name starts with/ends with/contains), and it makes it easier to see which filter fields are in use.

Preview records while building

To help you configure the view, there is a preview that returns a sample of your matched records. It updates as you update the query definition.

Owner association modes

Every MSP works in a unique way. Some MSPs assign tickets to members, while others set the owner of the ticket to a member. Previously TopLeft associated tickets with members based on assignments, but now you can choose how to associate tickets with members. For ConnectWise, you can choose either ticket owner or assigned members, and for Autotask you can choose either primary assignments only or also secondary assignments.

Grouping (swimlane) choice can be overridden

When setting up a view, you can choose the default way to group records on the board or Gantt chart. For example, you can group tickets by assigned member, priority, company, or a whole host of other options.

Users can override this choice when they view the board or Gantt chart.

Previously, if you wanted to use more than one way to group tickets, you needed to make one board for each choice. This would result in having multiple boards that were nearly identical. But now because the choice can be overridden, you can just make a single board and let users override the choice as they see fit.

Automatic per-person Work In Progress limits

When using Work In Progress limits, per-person limits are automatically used when grouping work by assigned person. In the old UI, per-person limits needed to be configured separately.

Column/status mapping is optional

In the new version, the relationship between Gantt charts and Kanban boards has been simplified. Since Gantt charts don't make use of the mapping of ticket statuses to columns, performing this mapping is an optional step. You only need to map statuses to columns if you intend to use Kanban boards.

Improvements for Board Users

The following improvements help engineers and managers make better use of Kanban boards and Gantt charts.

Free text search

Enter a search term to quickly filter the results on the Kanban board or Gantt chart.

Easily change the grouping (swimlane) field

If the default grouping (swimlane) field choice isn't to your liking, you can easily choose a different grouping.

Filter to multiple members, companies, or projects

You can drill into work for certain members, companies, or projects. In the old UI, you could only select a single member, company, or project, but in the new UI you can filter for multiple records.

Faster performance

The board view loads faster than before, especially on boards with hundreds of tickets. In one of our tests, loading time was reduced by 65%.

Full screen mode

There's a new full screen mode that removes the navigation menus to let the board take the most space on your screen.

Zoom into any column or group

You can drill into groups or columns of cards with a single click.

Improved ticket editor

The ticket editor provides options for managing more data about tickets.

Historic charts for any view

You can now view historic ticket counts for any board. In the old UI, it was only possible to see this data for a single board for each team.

Dark mode

Dark mode is supported throughout the app.

What's Still To Come

We continue to work on the new UI. Some of the things still to come are:

1. Autotask ticket+task boards: show service tickets and project tasks together in one board on the new UI
2. UDFs: support for User Defined Fields from the PSA
3. Client portal: Let client portal users use the new UI
4. Metrics: summarize ticket metrics in groups and column- for example, show the average number of logged hours in the In Progress column

Watch this space!

This space has been quiet for a while. We haven't disappeared! We've just been working hard on some really big improvements. One is support for HaloPSA. The other is a whole new UI.

Familiar, yet different. And yes, that's dark mode, our top requested feature. We will have announcements about this soon. If you just can't wait, and want to try out the new UI now, email us at help@topleft.team.

By the way, if you want regular content about making work flow in your MSP, subscribe to our YouTube channel: https://www.youtube.com/@TopLeft

Recent ConnectWise Improvements

We do have a few improvements to share about our ConnectWise support. Here are some things we've changed:

1. Email notifications to contacts have more customization options. When technicians make notes on tickets, an email can be sent to the ticket contact, and previously only a single template was supported. But now you can create a different email template for every ConnectWise board. This is especially useful if you have a unique template for the ConnectWise board for that one special customer. Docs are here: https://help.topleft.team/knowledge/configure-emails-sent-to-connectwise-contacts
2. In the ticket creation dialog, priority and contact are now optional. If you leave the fields blank when you make a ticket, ConnectWise will choose the appropriate defaults.
3. In Kanban boards for projects, when the swimlanes are project phases, the phase WBS code appears in the swimlane header.
4. Ticket SLA times are now available from the ConnectWise API, so we use their values instead of calculating everything ourselves. This should make things more reliable... even in the case of leap years. 🤪

Those who use TopLeft for ConnectWise now have a new way to filter the tickets that show up on a Kanban board. You can select tickets where you are a member of the ticket's company's team in ConnectWise.

This limits the tickets on your board to only those for companies you are responsible for. It's especially useful for account managers or project managers.

To use this filter, click Filters in the main menu:

TopLeft can now send messages to your clients and technicians with a From address at your own company domain.

TopLeft sends emails to your clients and technicians in a few circumstances. For example, emails are sent when a contact is invited to the client portal, or when technicians enter notes on a ticket, or when a technician is assigned to a ticket.

Previously TopLeft sent these emails with a From address of noreply@topleft.team and a Reply-To header of some address at your company. This was to ensure high delivery rates and minimize the configuration you needed to do to use TopLeft.

However, now TopLeft can send these messages with a From address at your own domain. This will make messages more recognizable for your clients and technicians.

If you'd like to send emails with the From header instead of Reply-To header, please contact the helpdesk. You will need to create DNS records in your email domain as part of the setup.

Autotask can show notices about companies in the ticket editing page. For example, a company may have an agreement that only a specific individual is permitted to approve work. This notice is shown on all tickets for the company so engineers are aware.

TopLeft can now show these notices. This will help your engineers be confident they can work from TopLeft without missing out on important company information.

When a notice exists for a company, an alert icon is shown on the company label on the card.

The full notice is shown in the ticket editor.

You don't need to take any action in TopLeft for these notices to be shown.

We have refreshed our infrastructure, so if you have an on-premise ConnectWise Manage server behind a source-filtering firewall, please update your whitelist. This applies to all regions. The new list of IPs is available in the knowledgebase.

We're delighted to announce the TopLeft dashboard. The dashboard gives historical context on your workflows, summarizes the work on each Kanban board, and highlights bottlenecks in your teams.

This feature is being released with the Teams feature we announced last week.

The dashboard is organized by team. The boards for a user's teams are shown on the My Boards tab so it's easy to find the most relevant dashboards.

The dashboard for a team's main Kanban board shows the following info:

• Card volume trend: shows the daily count of cards on the board over the last four weeks, including the number of cards with warnings (orange labels), errors (red labels), and the total count of cards.
• Cards: the current count of warning, error, and total cards.
• Workflow delays: for each column on the board, the average length of time the cards have been in the column.
• Top swimlanes: for swimlane boards only, it shows the swimlanes with the most cards, as well as the count of warning and error cards.

For boards that aren't the default for the team, much simpler metrics are shown. The dashboard simply shows the current number of warning, error, and total cards on the board.

If TopLeft doesn't automatically choose the best board for a team to show the detailed metrics, the correct board can be selected on the team's configuration page.

The following links are shown for each board:

1. Open: navigates to the Kanban board
2. Open Mine: navigates to the board with filters already applied to show only the user's own work. Using this link can make the Kanban board load quickly even when the unfiltered board has many tickets and takes a long time to load.
3. Edit: navigates to the board edit page (shown to team managers and administrators only)

To get to the dashboard, simply click on the TopLeft or company logo in the main navigation menu.

Here's how the dashboard can help MSPs:

• For managers and dispatchers: shows how a team's ticket counts change over time, highlights boards with many error or warning cards, and indicates which columns or swimlanes could be bottlenecks.
• For engineers: helps to focus on the boards most relevant to the user and to ignore boards for other teams, shows on which boards the user's work appears, and makes it easy to open a board already filtered to show the engineer's own work.

Metrics are recorded nightly. They are not updated in real time. But we've been recording the metrics for a while already so you'll have useful data as soon as the feature is enabled.

Recommended Actions

We previously recommended creating at least two boards for each team:

1. a board with swimlanes for assigned engineers
2. a board without swimlanes

This was because there was not previously an easy way for an engineer to use the engineer swimlane board to see only his or her own work.

However, with the addition of the "Open Mine" button and a recent change to how swimlane boards appear when filtered, it's no longer necessary to have a separate engineer swimlane board and non-swimlane board. Engineers can view their own work very easily from the swimlane board by using the "Open Mine" button on the dashboard.

If your team has two boards, an assigned engineer swimlane board and a board without swimlanes, you can delete the board without swimlanes and have the engineers use the swimlane board for their own work.

Further Reading

Dashboard documentation is available in the knowledgebase.

You can now organize your staff and Kanban boards into teams in TopLeft. This makes it easy for staff to know which boards are relevant to them, and makes access control and configuration much more flexible.

This will be released to customers over the next week. If you'd like to try it right away, email help@topleft.team.

We are also introducing a metrics dashboard, closely integrated with the teams function. Watch this space for that announcement very soon!

Teams are used in a variety of places in TopLeft, offering an improved experience for everyone. Here's how teams can help:

Improved Navigation

In the main menu, boards are listed by their teams, and each user's assigned team(s) are listed first. The boards relevent to each user are listed at the top.

Improved Board Setup and Dispatching

Using teams makes it easier to configure and use the Kanban boards, in two ways:

• A board can be filtered to only show work assigned to people in the board's team. This means when people join or leave a team, it's no longer necessary to change the filters on all the team's boards- just change the team membership in one place, and the boards are updated automatically.
• When assigning members to a ticket, the members available to assign are limited to the board's team members. The dispatcher doesn't need to choose from the whole list of TopLeft users.

Access Control

Teams can be used to restrict access to boards in two ways.

1. Individual boards can be restricted so they are only available to members of the board's team.
2. A new app-wide setting can restrict all boards to members of each board's team. This changes TopLeft from a default-available access mode to a default-restricted mode.

Learn more in the knowledgebase.

This access control method will replace the "security groups" method in TopLeft. The old method is still supported but will be phased out soon.

Flexible Management of Boards

Users no longer need to be a full administrator to create or update boards. A manager of a team can create, edit, and delete boards for the team, withouth being an administrator.

How to Use Teams

There are two steps to use teams in TopLeft.

1. Create a team and specify managers and members.
   As an administrator, on the settings page click Teams.
   
   
   In the Create a Team form, enter the team name, then click Create. Then you can choose the manager(s) and member(s) of the team. Managers will be able to create and update boards for the team.
   
   An individual can be a manager or member of many teams.
2. Assign one or more boards to the team. On the edit page for a board, go to the Teams tab and choose the team the board belongs to.
   
   

Learn more about managing teams in the knowledgebase.

Recommended Actions

In addition to following the above steps to organize your members and boards, we have a few recommended actions:

1. If you have Kanban boards that use filters for assigned members that are part of a team, change the boards from specifying specific members to using the "filter to team" option. This will allow you to change the filters for many boards at once by changing the team membership.
2. If some users have been given administrative permissions so they are able to manage boards, but they don't need to manage site-wide settings, remove their administrative permissions and instead make them a manager of one or more teams.
3. If you use the security groups function to limit access to boards, migrate to the new teams-based restrictions instead.

We hope this function is helpful. If you have questions, email help@topleft.team.