Catalog settings

Catalog settings cover the reusable material a project draws on: response templates, modules imported from elsewhere, modules this project publishes, trace metadata, and telemetry export.

Templates

The Template Catalog holds the response formats agents can send. It’s a reference you copy from rather than a place you author. Open a template to see how it renders, adjust its payload, and copy the snippet your agent needs. Navigation: Project -> Settings -> Templates

Find a template

Search by name, or filter by category. The categories group templates by the job the response does rather than by the channel it targets.

Category	Description
Content	Templates carrying formatted text and structured message payloads, including formats specific to a single messaging platform.
Media	Templates whose payload is a file the client plays, displays, or offers for download.
Data	Templates presenting numeric or tabular information, where the point is the figures rather than the prose around them.
Input	Templates collecting a response, where the agent expects the user to act on the message rather than only read it.
Feedback	Templates gathering a rating or reporting progress back to the user.

Reading a template card

Each card carries the template name, a short description, its category, and three badges. The badges are the part to read before you commit to a template, because they tell you whether it will work where your agent actually runs.

Badge	Description
Web	Reports how the web chat surface renders the template. A native value means the surface renders the template’s own form. Anything else means it renders a substitute, so the agent still responds but the user doesn’t see the layout the template describes. Weigh this alongside the channels your agent serves, since a template built for one messaging platform necessarily degrades elsewhere.
Preview	Reports how the catalog’s own preview pane renders the template, which isn’t always how the live surface renders it. A limited preview is a limitation of this page rather than of the template, so don’t rule a template out on the preview alone.
ABL	Reports whether you can emit the template from ABL. An insertable template is one you can send directly. A preview-only template can be inspected here but has to reach the user by another route, and a partial value means only some of the template is available. Check this badge first when you’re choosing a template to build on.

Inspect and use a template

Selecting a card opens a detail panel that takes you from looking at a template to sending one. Its three parts let you see the rendering, change the content, and take away the code.

Section	Description
Preview	Renders the template from the payload currently in the editor, so you can see the result before you write any agent code.
JSON Editor	Holds the template payload, which you can edit to try your own content in place of the sample. A character count below the editor shows how much of the allowed payload size you’ve used.
ABL Snippet	Gives the ABL that produces this template. Select Copy and paste it into your agent, then replace the sample values. This is the fastest route from choosing a template to sending one, and it saves you deriving the syntax from the payload by hand.

Imported modules

The Imported Modules page lists the reusable components this project has taken from the catalog or from other projects, including agents, tools, and workflows. Navigation: Project -> Settings -> Imported Modules Each entry records the module name, its version, the project it came from, and when this project imported it. The version and source together are what matter during an upgrade, since they tell you whose change you’re taking on and who to ask before you take it.

Module publishing

The Module Publishing page turns this project’s agents, tools, and workflows into modules other projects can import. Navigation: Project -> Settings -> Module Publishing Publishing places a module in the workspace catalog, where you choose the resources to include, set the version, and control who can import it. Treat a published module as an interface rather than a copy, because projects that import it inherit your future versions along with the current one. A release exports the agents, tools, and workflows you selected. Workflows come across in two forms: those you published directly, and those a published workflow tool depends on. The second kind travels whether or not you selected it, so review a release for dependencies you didn’t intend to share.

Trace dimensions

The Trace Dimensions page defines the custom metadata the platform records with every trace event. Navigation: Project -> Settings -> Trace Dimensions Each dimension carries a name, a source, and a data type. Dimensions become filters in the session browser and in Insights, so define them around the questions you expect to ask, such as the customer segment or the campaign behind a conversation. A dimension you add today applies to traces recorded from that point on, which makes this a setting worth getting ahead of rather than reaching for once you need the analysis.

Telemetry export

The Telemetry Export page sends this project’s live model, agent, and tool telemetry to an external observability provider, so agent behavior appears alongside the rest of your infrastructure monitoring. Navigation: Project -> Settings -> Telemetry Export

Destination

This section holds the provider connection and decides how much telemetry leaves the platform. Complete it before you enable export, since the status switch has nowhere to send to until you do.

Field	Description
Connection string	Holds the Azure Monitor connection string, which needs to carry both an instrumentation key and an ingestion endpoint. The field masks the value once saved.
Data export level	Decides how much leaves the platform. Metadata covers models, token usage, latency, and tool names. Full content adds prompts, responses, and tool inputs and outputs, which makes your observability provider a second store of conversation content and brings it into scope for the same privacy review as the platform itself.
Trace grouping	Decides what one trace represents. Grouping per session gives you the whole conversation in a single trace with each turn nested inside it, which suits reading conversations end to end. Grouping per turn gives accurate duration and status on each trace, which suits alerting and latency work.
Status	Turns export to the configured destination on or off without discarding the configuration.

Provide an Azure Monitor connection string before you save a new telemetry exporter.

Page actions

Three controls at the foot of the page manage the configuration you’ve entered.

Action	Description
Validate	Checks the destination details you entered. Run it before saving, since an unreachable destination silently drops telemetry rather than reporting an error later.
Save	Writes the exporter configuration to the project.
Reset	Returns the form to its last saved state.

Workspace settings

Project settings

Templates

Find a template

Reading a template card

Inspect and use a template

Imported modules

Module publishing

Trace dimensions

Telemetry export

Destination

Page actions

​Templates

​Find a template

​Reading a template card

​Inspect and use a template

​Imported modules

​Module publishing

​Trace dimensions

​Telemetry export

​Destination

​Page actions

Templates

Find a template

Reading a template card

Inspect and use a template

Imported modules

Module publishing

Trace dimensions

Telemetry export

Destination

Page actions