What's New in This Release

user management standardized idp identification via alias identity provider (idp) identification now uses aliases exclusively support for identifying an idp using an email address has been removed for more information see turbine login and authentication methods multi account access for turbine cloud turbine now supports multi account access that enables organizations to grant temporary, permissioned access to swimlane personnel such as support or services teams, without requiring them to be onboarded as account users this feature enables efficient collaboration for troubleshooting and issue resolution access is fully controlled and can be revoked at any time, simplifying support interactions while maintaining security and oversight for more information, see collaborating with swimlane users https //docs swimlane com/turbine/settings/collaborating with swimlane htm custom domain support for turbine cloud turbine now supports custom domain configuration, allowing organizations particularly mssps to use their own domain (for example, automation company com) to access their environment this enhancement improves brand consistency, strengthens security posture, and delivers a seamless user experience for both internal teams and external customers ssl certificates are fully managed, ensuring secure and hassle free setup for more information, see custom domain section in general settings canvas sensitive data handling with one click canvas now supports sensitive data handling with a single click inputs and outputs across all data actions—including webhooks, variables, and http actions—can be marked as "sensitive," signaling the system to mask this information in the user interface and logs once marked, sensitive data is automatically hidden in the playbook run page, test console, activity tab, test result view, events page, and logs the json builder ui now visually indicates fields marked as sensitive for both inputs and outputs the system checks all action input/output schemas to ensure sensitive values are obfuscated in run results webhook payloads flagged as sensitive are also masked in the events page no sensitive information will appear in api logs or other ui elements this feature enhances security by preventing exposure of confidential information and helps meet compliance and audit readiness standards this feature is behind a feature flag to enable, contact your csm orchestration insights dashboard and notifications a new orchestration insights page has been added to provide visibility into all playbook failures and timeouts stakeholders can be registered to receive email notifications for failures, timeouts, and infinite loop scenarios each email includes a direct link to the relevant playbook run, allowing quick access to detailed failure information this feature enables proactive issue resolution and improves overall visibility into playbook execution for more information, see orchestration insights https //docs swimlane com/turbine/orchestration/orchestrational insights htm new native action export record the record export action allows users to export a specific range of records from a larger dataset and returns the results as a csv attachment with built in pagination support, it enables precise control over which records to retrieve by fetching only the necessary data, it reduces system load and improves performance, while also allowing users to access relevant record sets without over fetching for more information, see export record pagination support for search records native action the record search ui now supports range based queries with the addition of two new input fields page number and number of records this enhancement enables precise pagination, allowing users to retrieve specific subsets of records—such as the first 1,000—more efficiently it improves performance by narrowing searches to defined ranges, reducing system load and response times, and offering better control when working with large datasets for more information, see search record https //docs swimlane com/turbine/turbine canvas/orchestration/search record htm content library gitlab integration turbine now supports external gitlab repositories in the content library enabling customers to configure an external gitlab repository using a gitlab project access token this work expands turbine’s capabilities to support both gitlab and github external repositories for content syncing and backup, providing more options to swimlane customers to use their preferred git tool for more information, see git integration https //docs swimlane com/turbine/settings/git integration/git integration htm persistent git repository storage git repository data storage has been enhanced by moving to a persistent shared volume, resulting in improved performance, increased stability, and more reliable backup capabilities hero ai companion user feedback collection users can now rate the quality and accuracy of hero ai companion responses users can select a thumbs up or thumbs down icon to indicate whether hero ai companion’s response adequately answered their questions users can also optionally add additional details in freeform text users may choose to include their most recent prompt and response a "learn more" tooltip clearly outlines what data is collected during feedback submission and how the data will be used by swimlane copy response users can now select the “copy” icon to copy individual responses from hero ai companion chat window to clipboard, enabling users to reference and use the response elsewhere for more information, see hero ai companion usage dashboard the usage dashboard has been enhanced to offer deeper visibility into automation activity and system behavior users can now view all flows associated with each playbook and access detailed run information directly from the dashboard new metrics include the average number of hero ai prompts per day across swimlane llm or openai and the average number of events per day, all filterable by date range these additions help users better understand usage patterns and platform performance for more information, see usage dashboard https //docs swimlane com/turbine/metrics dashbords/dashboards htm