> For the complete documentation index, see [llms.txt](https://support.suptask.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.suptask.com/getting-started/product-release-notes/2026/september-2026.md).

# September 2026

This release connects Suptask to your identity, device and HR systems, and lets AI Assistants act on them from the ticket.

Assistants can now answer repeat questions from your own knowledge, tag and prioritize incoming tickets, and be set up from ready-made templates in the Use Cases Library.

### Six new connectors

**New connector** · Web app (setup) and Slack

Suptask now connects to Microsoft Entra, Okta, JumpCloud, Iru (formerly Kandji), PDQ Connect and HaileyHR.

* **Microsoft Entra and Okta** – look up a user's account status, MFA methods and last sign-in.
* **JumpCloud** – manage users, devices and groups.
* **Iru** – assign devices and apply Blueprints.
* **PDQ Connect** – check installed software and vulnerabilities on a device.
* **HaileyHR** – pull start dates, departments and managers.

Every connector works for both agents and AI Assistants, so lookups and fixes happen in the ticket thread.

***

### Auto-tag and prioritize

**New** · Web app (setup) and Slack

An Assistant reads each incoming ticket, picks the closest Tag and Priority from your Form, and applies them – with a short note to agents on which sentence in the request led to that choice.

The Assistant only chooses from the values already defined in your Form, so filters, reports and SLAs keep working. Start in agent-review mode and switch to automatic once the choices look right.

***

### Auto-answer requests

**New** · Web app (setup) and Slack

An Assistant finds the answer to a request in your own knowledge – documents uploaded to Suptask, or Notion, Confluence and Guru – and resolves it. It can ask a clarifying question, follow up with the answer, and let the requester resolve the ticket or escalate to an agent who receives the context already gathered.

Answers are grounded in your sources only. You choose whether agents review suggested answers before they are sent, or whether the Assistant replies directly.

***

### Use Cases Library

**New** · Web app

The Use Cases Library contains ready-made Assistants for common IT and People requests, each listing the connectors to enable and the instructions to paste. Templates at launch:

* **Route to the owner** – find who owns the system being asked about and tag them in the requester's thread.
* **Enrich new tickets** – add the requester's account, device and pending updates before an agent opens the ticket.
* **Unblock sign-ins** – diagnose "I can't log in" from Entra or Okta and propose one fix.
* **Onboard and offboard** – prepare accounts, groups and devices across your HRIS, directory and device tool.
* **Answer HR questions** – time-off balances from your HRIS, policy and payroll dates from your documents.

Copy a template into your Inbox, replace the placeholders with your own names, and test it before you deploy.

{% hint style="info" %}
Every tool an Assistant can use is set to **Off**, **Ask** or **Auto**. Start read-only, let agents approve changes until you trust the results, then move routine tools to Auto one at a time.
{% endhint %}