---
schema_version: "1"
id: 5c42818137832c00c143e7465e4b94c5520b57ebf1e9eb5f5e6e23badac7f0ad
title: Omnistudio
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/264-0-0/rn_omnistudio.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_omnistudio.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 4b512c058cadbe5a1a5b773c50020fb849ffa6d200d21609b3d6e944d083acbb
description: Omnistudio provides a comprehensive, low-code suite of services and components, designed to build engaging, industry-specific digital experiences. It accelerates the path from development to production, enabling you to create guided customer interactions by using data from Salesforce and external sources.
products:
  - Cross Cloud
release: "264"
---
# Omnistudio

Omnistudio provides a comprehensive, low-code suite of services and components, designed to build engaging, industry-specific digital experiences. It accelerates the path from development to production, enabling you to create guided customer interactions by using data from Salesforce and external sources.

- **[Control Which Objects Guest and Community Users Can Query in Omnistudio](https://help.salesforce.com/s/articleView?id=release-notes.rn_flexcard_datasource_allowlist.htm&release=264.0.0&type=5)**  
    Protect your org data by specifying which objects Experience Cloud guest users and authenticated community or portal users can query through Omnistudio. Omnistudio now blocks SOQL queries and SOSL searches that external users run through the HandleData() and HandleDataCards() methods unless every object in the query is on an allowlist that you maintain. Allowed queries run in user mode, so the user's object permissions, field-level security, and sharing rules apply.
- **[Simplify Omnistudio Component Deployments with Clean Metadata](https://help.salesforce.com/s/articleView?id=release-notes.rn_omnistudio_clean_metadata_deployment.htm&release=264.0.0&type=5)**  
    Use Clean Metadata Deployment to manage and deploy Omnistudio components with the same tools and processes you already use for standard Salesforce metadata. Deploy them by using Salesforce CLI, change sets, and first-generation (1GP) and second-generation (2GP) packages in the same pipeline as your Lightning web components, flows, Apex classes, and similar metadata. Each component exposes a single version, dependencies are detected automatically, and source files use clean, version-agnostic names. Previously, deploying Omnistudio components required extra steps to work around the limitations of the old metadata.
- **[Reuse Autolaunched Flow Logic Across Your Flexcards (Generally Available)](https://help.salesforce.com/s/articleView?id=release-notes.rn_omnistudio_flexcard_autolaunched_flow.htm&release=264.0.0&type=5)**  
    Set an active autolaunched flow as a Flexcard data source or invoke a flow directly from a Flexcard action. Reuse existing autolaunched flow logic across your Flexcards to keep business logic centralized. The autolaunched flow data source is available in the Omnistudio standard designer.
- **[Run Flexcards and Omniscripts Offline on Mobile Devices](https://help.salesforce.com/s/articleView?id=release-notes.rn_omnistudio_flexcard_omniscript_offline_mobile.htm&release=264.0.0&type=5)**  
    Keep field work moving in areas with poor or no connectivity. Your mobile users can open, complete, and submit Flexcards and Omniscripts entirely offline, without waiting on live server calls or timing out in remote locations. Data operations, input validations, and calculations run on the device. Completed actions queue locally and sync to Salesforce in sequence after a connection returns.
- **[Omnistudio Minor Releases](https://help.salesforce.com/s/articleView?id=release-notes.rn_omnistudio_updates_minor_releases.htm&release=264.0.0&type=5)**  
    Find out about bug fixes, minor updates, and known issues about Omnistudio made after Summer '26 and before Winter '27.