What's New

Early Access (EA) pre-release notification: Edit of multiple computers (standard and custom fields) in SAM on Snow Atlas

We would like to announce the Early Access availability of Computers Multi-Edit in SAM Core on Snow Atlas.

Release summary: Edit of multiple computers is now live in SAM on Snow Atlas. This enhancement enables you to update standard fields and custom fields on multiple computers in a single operation, directly from the Computers list, eliminating repetitive manual updates and reducing reliance on APIs, imports, or technical support.

Release info:

• Release date (EA): Planned - 5th November 2026 (afternoon) -
• Product domain: SAM on Snow Atlas
• Release availability: Early Access (EA) - enabled per tenant, on request behind a feature flag.

What's included? 

• Multi-editing capability: Select and update up to 10,000 computers in a single operation from the Computers list.
• Standard field updates: Update Status, Automatic quarantine management, Organization and Auto editing across all selected computers.
• Custom field updates: Update, clear or remove custom field values across all selected computers, including text, number, decimal, date, currency, Yes/No and list fields.
• Review before saving: A Confirm changes summary shows exactly which fields will be updated, and for how many computers, before anything is saved.
• Background processing: Large updates run in the background, with a progress banner on the Computers list and a clear success or failure message when the update completes.
• Safe updates: Each computer is updated as a whole. If an update cannot be completed for a computer, none of its changes are applied, so no record is left half-updated.
• In-app experience: Perform all updates directly from the Computers list without APIs, imports, or external tools.
• Permission consistency: Use existing edit permissions with no additional configuration required.
• Audit log support: Multi-edit updates are recorded in the audit log, providing visibility into changes made across computers.

For each computer value or setting: Only changed values are updated. Every field stays grey until it is modified; once modified it turns dark and is marked Modified. Anything still grey will not be written. If the selected computers share the same value, it appears in the edit view. If the selected computers have different values before the change, you will see "Values differ" in the edit view. If every selected computer is blank, you will see "No value". To undo a change to a custom field before saving, remove the field and add it back; it returns to its original value.

Why this matters? 

• Restores a capability customers lost: multi-edit of computers existed in SLM and has not existed in Atlas since the legacy Search for Computers page was hidden. 
• Simplifies organizational changes: Move hundreds of computers to a new organization node after mergers, acquisitions, restructures, or team changes. 
• Keeps the estate accurate: Set the status of many computers at once, for example marking retired or unused devices as Inactive, and manage quarantine and auto editing settings consistently. 
• Maintains custom metadata at scale: Update fields such as warranty dates, departments or cost information across many computers without editing each record. 
• Accelerates data cleanup initiatives: Correct outdated or inconsistent computer information across large numbers of computers in one operation. 
• Reduces technical dependency: Enables users to perform large-scale updates directly in the product without relying on APIs, imports, or technical teams. 
• Saves significant time: Activities that previously required numerous manual updates can now be completed in a single operation, freeing teams to focus on compliance and optimization.

Scope: Multi-edit applies one value across a selection. If you need to perform different values per record, operations above 10,000 records, and scheduled or automated updates, continue to use imports and write API's work.

Known improvements required: 

• We are working on improving the performance on shared tenants to allow parallel editing. Larger values of 10000 computers and include custom fields may experience timeouts during EA. For testing purposes, please aim to reduce selected computers quantity in a single edit until GA.
• Improve the refresh of edited data to fully sync. Users on EA may be required to manually use the "update data" button on the bottom of the Computers list page.

Activities before GA:

• Plan: Release to only selected EA customers who notify their Flexera representatives of wishing to try this feature. 
• Monitoring: Tracking of edits are in place to understand and monitor usage, as well as frontend monitoring of user behaviour to ensure we can provide the best experience possible.
• Feedback required for validation: We want your EA feedback before going GA. What works well, what is still missing, further improvements, or perhaps a need for utilising features in other parts of the product?
• Concurrent multi-tenant performance: Operations close to the 10,000 cap running concurrently across tenants have been observed to have degraded performance, hence the limited selection of EA tenants.

What's next? 

• Edit of multiple applications (including custom fields). 
• Edit of multiple licenses (including custom fields). 
• Edit of multiple users (including custom fields). 
• Edit of multiple agreements: extension to include custom fields.

How customers get access: Early Access is enabled per tenant on request. We do not switch it on for anyone who has not asked. If you would like to have this added to your tenant, please reach out to your CSM representative, Account Manager, or Support.