Containers and scopes

Some pages in XTM One are about one specific object. Others are about a container that groups many objects, or a scope that sets a visibility boundary.

Containers

A container is any object or view whose main role is to hold and organize related work. It usually shows the items it contains and lets you add or remove them. The main ones:

• Conversations keep the messages, context, and history of one chat thread together.
• Knowledge bases group documents and import sources into one searchable corpus.
• AI Catalog entries group shareable resources into published packages that other users can review and clone.

Being inside a container does not always mean ownership: a prompt attached to an agent is still reusable elsewhere, and a catalog item added to your account usually becomes a new local copy rather than a live link to the source.

Scopes

A scope is the boundary that decides where an object is visible and who can edit it:

• Personal — belongs to one user; the safest place to experiment, since edits stay local.
• Group-shared — visible and editable by members of the selected group; a collaboration scope, not read-only publication.
• Company-managed — visible to everyone but usually edited only by admins; the broadest scope in day-to-day use.

Before you change something

Ask whether you are editing the container itself or an item inside it, and whether the change affects only you, your group, or the whole company. Those two questions prevent most accidental changes.

Next step

Continue with Reuse and deduplication, which explains when XTM One keeps a shared object, when it creates a copy, and how to avoid duplicate setup.