> ## Documentation Index > Fetch the complete documentation index at: https://docs.serval.com/llms.txt > Use this file to discover all available pages before exploring further. # October 30, 2026 > Control integration access within a workspace, customize task types and statuses, and sync SharePoint site pages as knowledge. ## Highlights * [Control integration access within a workspace](#control-integration-access-within-a-workspace) * [Create custom task types](#create-custom-task-types) * [Add custom task statuses](#add-custom-task-statuses) * [Sync SharePoint site pages as knowledge](#sync-sharepoint-site-pages-as-knowledge) ### Control integration access within a workspace You can now lock down sensitive integrations, such as production AWS or Okta, so that only workflows in specific packages can use them. Only the people on a package's access list can publish changes to those workflows. Create a package in **Settings → Packages** and add the people who can publish to it. Then, on the integration's **Settings** tab, choose **Only workflows in these packages**. A preview shows which workflows would lose access, so you can move them into the package first. Integration access scoping is opt-in. Every workflow starts in its team's Default package and every integration starts open, so nothing changes until someone with the **Manage Integration Access** permission restricts a connection. *For example, restrict your production AWS connection to an Infrastructure package so that your platform team can build workflows that can act on it.* ### Create custom task types By default, tasks are built-in ticket types. Now, you can create custom task types with their specific status lifecycle and fields. Each task type can be a child of specific parent ticket types. When you add a task to a ticket, select from the custom task types allowed under that ticket type. *For example, a security team adds a Remediation custom task type that can only be a child ticket of incidents and problems.* ![Remediation custom task type page listing the ticket types its tasks can be a child ticket of, above its Lifecycle, Fields, and Priorities tabs](https://mintcdn.com/serval/20acimYESca0jrhz/images/serval-docs/ticketing/tickets/task-type-page.png?fit=max\&auto=format\&n=20acimYESca0jrhz\&q=85\&s=ba26dc04f799f2dc44ccc0e7beaea535) Set them up in **Team Settings → Ticket Types → Task**, which now lists Task and your custom task types under **Task types**. The built-in Task type's fields and priorities moved there too: select **Task** in that list to edit them. See [Task types](https://docs.serval.com/sections/documentation/ticketing/ticket-configuration/tasks.md#task-types). ### Add custom task statuses Tasks are no longer limited to a fixed set of statuses. Add your own and edit them in **Team Settings → Ticket Types → Task**, the same way as for requests and incidents. Tasks of the built-in Task type can use every task status, and each custom task type picks the ones it moves through. *For example, add a "Waiting on vendor" status so tasks blocked on a third party stand out from tasks in progress.* ![Task ticket type settings with the Statuses card and its Add Status button above the Task types list](https://mintcdn.com/serval/20acimYESca0jrhz/images/serval-docs/ticketing/tickets/task-ticket-type-page.png?fit=max\&auto=format\&n=20acimYESca0jrhz\&q=85\&s=54b5bb1b90152655dcf4c8911bbfdfff) See [Task statuses](https://docs.serval.com/sections/documentation/ticketing/ticket-configuration/tasks.md#task-statuses). ### Sync SharePoint site pages as knowledge Serval can now sync a SharePoint site's pages as knowledge, not only its document libraries. In **Knowledge → Manage Sources → Choose items to sync → Choose SharePoint paths**, open a site and select **Site Pages** to include its modern pages. Serval reads each published page's text through Microsoft Graph and keeps the original page URL for citations. Serval also now ingests Markdown and plain-text files from SharePoint. See [SharePoint site pages](https://docs.serval.com/sections/integrations/microsoft-graph.md#sharepoint-site-pages). *** ## Workflows **Ticket-created events carry the original channel** Workflows that trigger on a new ticket now receive the channel the ticket came in on, so a workflow can branch on how a request arrived, such as email, Slack, or Microsoft Teams. ## Tickets **Sort ticket lists by SLA** You can now sort a ticket list by its SLA columns. Click an SLA column header in a team ticket list to sort tickets by how soon they breach, so the most urgent work rises to the top. Enable the columns you want from the **SLAs** heading in the **Display** menu's column picker. See [Filter and sort tickets](https://docs.serval.com/sections/documentation/ticketing/manage-collaborate/filter-sort.md). **Run an SLA action at breach** The SLA action timing menu now has an **At breach** preset, so an escalation or notification can fire exactly when an SLA target is missed, with no offset to set. **Consecutive access requests group into one card** When a ticket thread has several access requests in a row, Serval now shows them as a single batch card. Each request keeps its own approval and actions, and a one-request card opens straight to its access decision. **See assignment rules as a flow diagram** Assignment rules now have a read-only **Tree** view next to the editable **List**. The Tree shows how a ticket moves through the rules and combines neighboring rules into shared decisions, so you can follow the routing top to bottom. **Incidents and changes no longer use a due date** Incidents and major incidents no longer show a due date. Their urgency comes from priority and SLA. Changes are scheduled by their change window instead. **Pick impacted items from a filterable dialog** When you add the items a ticket impacts, you can now choose them in a filterable, multi-select dialog instead of picking one type and then one item at a time. Filter by item type and by that type's fields, select several at once, and add them together. **Request feedback in Microsoft Teams** When your team collects feedback on resolved requests, Serval now asks for it in Microsoft Teams as well, with an optional comment, matching how it already works in other channels. ## Databases **Color-coded table cells in dashboards** Table widgets on a dashboard now fill each cell with the color of its value. When a status, priority, or other categorical field has colors defined, every matching cell shows that value's color, so a table reads at a glance the way a chart does. Numeric cells stay unfilled. ## Integrations **New native integrations** Serval adds native connectors for [Azure DevOps](https://docs.serval.com/sections/integrations/azure-devops.md) and [OpenAI Admin](https://docs.serval.com/sections/integrations/openai-admin.md), plus [Dynatrace](https://docs.serval.com/sections/integrations/dynatrace.md), [Matrix42](https://docs.serval.com/sections/integrations/matrix42.md), and [Resilio](https://docs.serval.com/sections/integrations/resilio.md) in beta. **Figma plan access tokens** Figma connections can now authenticate with a plan access token, and the OAuth app no longer requests organization scopes. See [Figma](https://docs.serval.com/sections/integrations/figma.md). **Search base fields for Active Directory and LDAP** The connection form now has user and group search base fields, so you can point discovery at the directory subtrees you use. See [Active Directory (on-prem)](https://docs.serval.com/sections/integrations/ldap-ad.md). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.