Extension settings

After you create a shared extension model, you can change its settings in the model IDE.

Requirements

To change shared extension model settings, you’ll need:

A shared extension model
Connection Admin or Modeler permissions on the extension model

Updating extension settings

Click Develop in the sidebar and open the extension model.
In the model IDE, click Model > Advanced > Extension settings.
Change the settings.
Click Update. The change applies immediately.

Allow exploration

The Allow exploration setting controls whether users can select the extension as the model for new content, including Omni Agent chats.

Off (default) - The extension does not appear in the model list. The Explore button does not appear in the extension’s model IDE. Users cannot select the extension as the model for an Omni Agent chat. Omni can still route users to the extension with dynamic_shared_extensions.
On - The extension appears in the model list when a user creates a new workbook or Omni Agent chat. Users with access can query the extension with AI.

This setting does not grant access. You’ll still need to grant users access to the model.

Branch workflow

The Branch workflow setting controls how you develop and release the extension. See Branches and Git for extension models for the full behavior of each workflow.

	Develop with the parent model	Develop independently
Summary	Omni creates branches on the parent model. One branch carries changes to the parent and to its extensions, and goes through the parent’s Git repository if it has one.	A branch holds the extension’s changes in a layer on the extension itself, not on the parent model. The extension can link its own Git repository, separate from the parent model’s.
Best for	One central team owns the parent and its extensions. Changes need one review.	A separate team owns the extension and releases on its own schedule.
Where Omni creates branches	On the parent model. One branch contains changes to the parent and to every extension in this workflow.	On the extension itself. Changes to the extension don’t go through a layer on the parent model.
Who merges	Users who can edit the parent model, in one merge or pull request	Users who can edit the extension, in Omni or in a pull request on the extension’s repository
Git	Included in the parent model’s repository, under `<model path>.extensions/<extension name>/`	Optional. The extension links its own repository and has its own Git settings, which you open from Model > Advanced > Git settings. Omni writes its files to `<model path>.extensions/<extension name>/` by default.
Branch Mode required?	Yes, when the parent model is linked to Git	Yes, when the extension is linked to Git
Limitations	The parent model’s Git settings apply, including Pull request required and follower mode.	No branch-based schema refresh. No table migration on extension branches. To switch to Develop with the parent model, unlink the extension’s Git repository first.

Changing the branch workflow on a Git-linked model changes which repository Omni writes to and can leave an old folder behind. Read Changing the branch workflow first.

Next steps

Branches and Git for extension models - How each branch workflow behaves in Omni and in Git
Set up a shared extension - Create an extension, route users to it, and set access

Getting started

Manage content

Analyze & build

Visualize & present

Deliver content

Model data

Manage integrations

Extension settings

Requirements

Updating extension settings

Allow exploration

Branch workflow

Next steps

​Requirements

​Updating extension settings

​Allow exploration

​Branch workflow

​Next steps

Requirements

Updating extension settings

Allow exploration

Branch workflow

Next steps