> ## 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. # September 18, 2026 > Import access grants from a screenshot, author overnight SLA schedules, build richer routing and SLA conditions, rate a ticket from Slack on demand, and launch a journey from a catalog request. ## Highlights * [Import access grants from a screenshot](#import-access-grants-from-a-screenshot) * [Overnight and split-shift coverage in SLA schedules](#overnight-and-split-shift-coverage-in-sla-schedules) * [Richer routing and SLA conditions](#richer-routing-and-sla-conditions) * [Request ticket feedback on demand from Slack](#request-ticket-feedback-on-demand-from-slack) ### Import access grants from a screenshot When you import an application's access grants into Serval, you can now hand over a screenshot instead of a CSV. Drop in a PNG, JPEG, or WebP image of the app's members list, and Serval reads each row and turns it into a grant you can review, map, and confirm before anything is imported. ### Overnight and split-shift coverage in SLA schedules A schedule's weekly hours can now hold more than one time range per day, and a range is allowed to end at midnight. That makes overnight and split-shift coverage possible: chain a range that ends at midnight on one day with one that starts at midnight on the next, or give a single day a morning and an afternoon window with a gap between them. *For example, model overnight support by pairing an 11:00 PM to midnight range with a midnight to 6:00 AM range on the following day.* See [Schedules](/sections/documentation/ticketing/ticket-configuration/schedules). ### Richer assignment and SLA conditions Assignment rules and SLA conditions can now match on several values at once and offer more ways to compare them. A condition can match any of several labels, statuses, or requester groups, check whether a label is present, exclude a set of categories, and requester text conditions are typed as free text rather than picked from a fixed list. *For example, write one SLA that applies whenever a ticket carries any of several labels, or am assignment rule that skips a group of categories.* See [SLAs](/sections/documentation/ticketing/ticket-configuration/slas) and [assignment rules](/sections/documentation/ticketing/ticket-configuration/assignment). ### Request ticket feedback on demand from Slack Requesters no longer have to wait for Serval's automatic prompt to rate a ticket. In Slack, `/serval-feedback` opens the feedback form with a list of the requester's most recent tickets on teams that collect feedback. The rating scale, comment box, and file upload follow the selected ticket's team settings, so the form matches wherever the ticket lives. *For example, after a request is resolved, type `/serval-feedback`, pick the ticket, and leave a rating and a comment.* See [Feedback](/sections/documentation/ticketing/manage-collaborate/feedback) and [Slack](/sections/integrations/slack). *** ## Ticketing **Show several visibility groups in one list** A ticket list can now be narrowed to more than one visibility group at a time, so you can watch related queues together instead of switching between them. **Search connected tickets by their ServiceNow number** The ticket search boxes now match a connected ticket by its ServiceNow number, so you can jump straight to a ticket using the identifier your team already knows it by. ## Knowledge **Restore or delete an archived knowledge base** The Archive view now lets you restore or permanently delete a whole knowledge base, not just its individual pages. **Scope a GitHub knowledge source to repository paths** When you connect GitHub as a knowledge source, you can now limit the crawl to chosen repository paths before the first sync, so Serval only reads the folders you point it at. ## Workflows **Authenticate workflow webhooks with a bearer token** A workflow's incoming webhook trigger can now require a bearer token, giving you a standard way to authenticate the systems that call it. **Embed database file images in workflow emails** Workflow emails can now display images stored on database records inline, so a message can show a picture from your data rather than only linking to it. ## Journeys **Start a journey from a service catalog request** A service catalog submission can now launch a journey directly, instead of only opening a ticket. ## Integrations **New integrations** Serval adds four native integrations in beta: [BeyondTrust Password Safe](/sections/integrations/beyondtrust-password-safe), [BeyondTrust Privileged Remote Access](/sections/integrations/beyondtrust-pra), [Omnissa Workspace ONE UEM](/sections/integrations/omnissa-workspace-one-uem), and [HCL BigFix](/sections/integrations/bigfix). **Choose Jira permission scopes at connect time** The Jira connection flow now shows a permission picker, the same one Confluence uses, so a connection requests only the scopes it needs. Bring-your-own Atlassian apps no longer have to mirror a fixed, full scope list. ## For developers **Public API additions** The public API gains endpoints to create, read, update, and delete ticket statuses with portable IDs, configure a team's help desk channels, search a user's access memberships, submit ticket feedback, read attachment descriptions, set a message's created-at time, and read a database record's files. The create-ticket SDK helper can now also attach a workflow to the ticket it creates.