Skip to main content
Apps run in a sandboxed iframe with strict security controls by default. App-level settings let you enable specific features on a per-app basis, giving you fine-grained control over what each app can do.

​
Requirements

Editor permissions or higher on a document are required to edit app settings.

​
Accessing app settings

To access an app’s settings:
  1. In an app, click Edit to enter draft mode.
  2. Near the top left corner of the page, click the icon (located next to Code).

​
Capabilities

Controls what the app can do inside its sandbox.

​
Downloads

Grants the app’s iframe the allow-downloads sandbox permission, letting the app save files to the viewer’s device — for example, an Export CSV button. Your organization can turn downloads off for every app under Settings > Apps. When it has, this setting is replaced by a note saying so, and the app can’t save files regardless of what was set here.

​
Printing and dialogs

Allows the app to use the browser’s print function (window.print()) and native JavaScript dialogs (alert, confirm, prompt). Your organization can turn printing and dialogs off for every app under Settings > Apps. When it has, this setting is replaced by a note saying so, and the app can’t print or show dialogs regardless of what was set here.

​
Clipboard copy

Grants the app’s iframe the clipboard-write permission. This allows apps to include copy buttons that programmatically write text or values to the user’s clipboard. Along with enabling this setting yourself, the Omni Agent can enable it automatically when you ask it to add a copy button or clipboard functionality to your app. Your organization can turn clipboard copy off for every app under Settings > Apps. When it has, this setting is replaced by a note saying so, and the app’s code can’t write to the clipboard regardless of what was set here.
When an app with Allow clipboard copy enabled is itself embedded inside another product, the embedding iframe must also include allow="clipboard-write" for the grant to apply to the app. See Allow copying in embed iframes for more information.

​
Full screen

Lets the app’s own code call requestFullscreen() — for example, a “Present” button — via the browser’s fullscreen Permissions Policy feature. View > Full screen in the app menu keeps working whether or not this setting is enabled. Your organization can turn full screen off for every app under Settings > Apps. When it has, this setting is replaced by a note saying so, and the app’s code can’t enter full screen regardless of what was set here.
When an app with Full screen enabled is itself embedded inside another product, the embedding iframe must also include allow="fullscreen" for the grant to apply to the app. See Allow full screen mode in embed iframes for more information.
Controls if and where an app can open links, covering both external websites and pages inside Omni. Along with enabling these settings yourself, the Omni Agent can enable these settings automatically when you ask it to add links or navigation to your app.

​
Internal navigation

Allows the app to navigate to other pages inside Omni — for example, a link that opens a dashboard. This setting is independent of External links: you can allow internal navigation without allowing the app to open external links, and vice versa. Controls which external links can open in the app:
  • Any site - Apps can open external links to any site, meaning the app can open links to - and send data to - any site.
  • Restricted - Apps can only open external links for hosts specified in Restrict to following hosts
  • Disabled - Apps cannot open any external links.

​
Restrict to following hosts

Restricts where the app can open external links. Apps will be able to open links only to the hosts specified in this list. In the Restrict to following hosts field, enter one or more hosts. Add one host per line, or separate them with commas or spaces. Wildcards like *.example.com are allowed:
This allowlist follows the same formatting and validation rules as safe domains. See Domain formats for accepted and disallowed patterns. Forces external links to open in a new tab, keeping the app on the current page. This is the default. The External links setting must be enabled to configure this setting.

​
Hosts

Controls which external hosts apps can load resources from.

​
Safe domains

Optionally extends the app’s security model by specifying additional trusted hosts for loading images, video, audio, scripts, stylesheets, fonts, and network connections. By default, apps can load resources from a curated list of trusted CDNs (e.g., Google Fonts, jsDelivr) and Omni’s bundled charting, styling, and utility libraries. These are available regardless of your safe domain configuration.
Your organization’s external source policy sets the ceiling for this setting.

​
Configuring Safe domains

To configure safe domains for an app:
  1. Open the app’s settings.
  2. In the Safe domains section, toggle Allow safe domains on.
  3. Enter one or more domains in the Safe domains field. Add one domain per line or separate using spaces or commas:
    See Domain formats for formatting requirements.
  4. Click outside the text area to save. The domains are validated when you save.
Along with configuring safe domains yourself, the Omni Agent can configure safe domains when building or editing an app. For example, you can tell it “load images from cdn.example.com” and it will enable Safe domains and add the specified domain.

​
Disabling Allow safe domains

If you disable Safe domains, all external access (excluding map providers if Allow map providers is enabled) for the app will be disabled. Specified domains will be saved and can be re-enabled by toggling the setting back to on.

​
Domain formats

Safe domains accepts the following formats: Each domain must:
  • Have at least two labels (e.g., example.com is valid, but localhost or com alone is not)
  • Use only lowercase letters, digits, hyphens, dots, and optionally a leading *. wildcard
  • Be 253 characters or fewer
  • Include a valid port (5 digits or fewer, numeric) if a port is specified
For example:
Valid domains

​
Embedded frames

Allows the app to embed external sites as iframes, such as a public page or a tool hosted elsewhere.
An embedded site can receive the app’s query data, and the app can also navigate to it. Only add hosts you trust.
Your organization’s Embedded frame policy sets the ceiling for this setting. By default, the policy doesn’t allow embedded frames. In this case, the Embedded frames section explains that the app can’t add embedded frames, and an Organization Admin must change the policy first.

​
Configuring embedded frames

  1. Open the app’s settings.
  2. In the Embedded frames section, enable Embedded frame allowlist.
  3. In the Embedded frame allowlist field, enter one or more hosts. Add one host per line, or separate them with commas or spaces. Wildcards like *.example.com are allowed:
    If your organization uses a Custom frame policy, the section lists the hosts your organization allows. Hosts outside that list are flagged and won’t load.
  4. Click outside the text area to save.
Turning off Embedded frames blocks the listed hosts, but keeps the list so you can turn it back on later. Embedded frame hosts use the same formats as safe domains.

​
Organization-wide hosts

If an Organization Admin turned on Allow these hosts by default for the organization’s custom frame host list, every app can embed those hosts without configuration. In this case:
  • The section shows the organization’s hosts as read-only, and the toggle is named Customize embedded frames.
  • To limit the app to fewer hosts, turn on Customize embedded frames and edit the list. If the app doesn’t have its own hosts yet, the list starts with the organization’s hosts.
  • To go back to the organization’s hosts, turn off Customize embedded frames.

​
Blocked embeds

A site can still fail to load after you allow its host, if the site doesn’t allow framing, requires a login, or needs a page origin to load. Embedded sites run without cookies or a page origin. When Omni blocks an embed, the app shows a message over the empty frame that explains why. For example, embedded frames are turned off for the app, or the host isn’t allowed by the app or the organization.

​
Map providers

Allows maps in your app to render tiles from keyless map providers. Along with enabling this setting yourself, the Omni Agent can enable it automatically when you ask it to add a map to your app. When enabled, Omni widens the CSP to permit image and network requests to the following map providers’ tile servers and the CDNs their libraries load from. No additional setup is needed. Your organization can turn map providers off for every app under Settings > Apps. When it has, this setting is replaced by a note saying so, and the app can’t load map tiles regardless of what was set here.