An overview of Tecton outlet types and how they connect platforms with extensions.
Outlets are components that give extension authors a place to render their work within a platform. They generate an iframe and handle data passing between the iframe and the host platform. Adding new outlets provides new locations where extensions can be rendered.
There are four kinds of outlets:
Feature outlets take up the main content area of a page in a platform, and typically also require space in that platform's navigation. Feature outlets are the most common host for extensions. They use the <tecton-platform-outlet> element.
Widget outlets are a specialized form of feature outlet used for rendering extensions in widget locations across the platform (e.g., dashboard widgets, account detail widgets). Widget configuration is managed through the platform's theme files and admin tools.
For more information on developing widgets, see the Widget Development Guide in the SDK documentation.
Tab outlets render extensions as tabs within a tabbed interface. Multiple extensions can each contribute a tab to the same outlet. They use the <tecton-tabbed-outlet> element.
Tab outlets support context filtering, allowing tabs to appear only for specific account or transaction types. For example, a tab can be configured to appear only on Checking account detail pages.
For a detailed guide on implementing and configuring tab outlets, see Tab Outlets.
Contextual menu outlets render extension-provided actions as items in a dropdown menu. They use the <q2-dropdown> element with outlet-aware properties (context, contextValue, resolvedType, additionalContext) that allow menu items to be dynamically resolved based on the current context.
For a detailed guide on implementing contextual menu outlets, see Contextual Menu Outlets.
Extension developers configure their extensions into outlets using the Tecton CLI (q2 tecton). From the CLI, select Outlet Configurations to see the available outlet types:

The four outlet configuration options are:
For step-by-step CLI walkthroughs, see:
Outlets can filter which extensions appear based on the current context (e.g., account type, transaction type). This allows extensions to be shown only when relevant — for example, showing a rewards tab only for credit card accounts.
For details on configuring context filters, see UUX Content Controls.
Outlets can be nested inside extensions. This means an extension rendered in one outlet can itself contain outlet elements, allowing for deeper composition of micro-frontends.