Extensions

An Extension surfaces a Domino App at a mount point in the Domino UI: a link in the Project sidebar, an entry on a Dataset details page, an entry on a Model details page, an entry in the three-dot menu for files in a Dataset, or a new page in the Admin panel. Domino opens the App in a new tab and passes the context of the page the user came from as query parameters, so the App can act on the Project, Dataset, file, or Model that user was looking at. The App behind an Extension is yours to build. One App can back several Extensions, and pointing an Extension at a newer App version is a configuration change an admin makes, not a rebuild. Three requirements shape the App. It must have extended identity propagation enabled, which needs a framework that can read proxied HTTP headers: Flask and Dash support them by default, and Shiny needs Server Pro. A SysAdmin or CloudAdmin publishes it, and only Admins create the Extension itself. Viewers consent before the App can act as them. Create and manage Extensions covers the App requirements, the five mount points and the context each one passes, and the guidelines an Extension’s App should follow.

Extensions Domino publishes

These three Extensions are built on the same framework, and the source for each is public in the dominodatalab GitHub organization. An administrator installs, upgrades, or uninstalls any of them from the Admin panel, without building the App. See Install Domino Official Extensions.

Extension	What it does	Source repository
Clinical Data Explorer	Explore, filter, and visualize data through an intuitive web interface.	clinical-data-explorer
AutoML Studio	Train, evaluate, and deploy machine learning models through a unified no-code interface.	AutoML_Extension
Auto Model Documentation	Automatically generate professional ML model documentation from code and Experiment Manager artifacts.	AutoDocumentation_Extension

Core Concepts

Features

Extensions Domino publishes

​Extensions Domino publishes

Extensions Domino publishes