Swimlane Content, User Content, and Integrated Marketplace

ai soc includes components (for example, threat intelligence vendor interaction components) that also appear in the integrated marketplace how turbine tags content affects what the marketplace shows as installed the behavior content you install from library → swimlane content is tagged as swimlane content if the same logical content is moved to another tenant (for example, export and import, or promotion between tenants), the destination tenant typically treats that copy as user content , not swimlane content impact topic what to expect marketplace status the integrated marketplace may not show the item as installed on the destination tenant install can remain available overwrite risk choosing install from the marketplace when promoted content already exists may overwrite that content and tenant specific changes version drift installing or updating from the marketplace without comparing versions can introduce regressions or mismatches versus promoted content that was customized or pinned recommended practices scenario recommended action initial setup where possible, install ai soc and related marketplace items from swimlane content / marketplace in each tenant so tagging and update paths stay consistent promotion workflow if you rely on promoted copies, treat them as a snapshot do not reinstall the same marketplace package on top unless you intend a full reset or controlled upgrade version control before using install from the marketplace on a tenant that already has promoted content, compare marketplace version and behavior to what is already installed after content is migrated and treated as user content , the marketplace update path may not match promoted copies coordinate with your administrator before overwriting