Tessitura Settings Get A Cleaner Collection Model
Tessitura configuration moves into a collection-based app model, so settings, app state, and public theme data can be handled consistently across tenants.
Tessitura configuration moves into a collection-based app model. Settings, app state, and public theme data can now be handled more consistently across tenants rather than relying on global one-off configuration.
Scalable across multiple customers
This makes the Tessitura app easier to extend with TNEW, instance data, and customer-specific launch settings. As more tenants adopt Tessitura-powered sites, a collection-based model gives the platform a scalable way to manage per-tenant configuration without bespoke workarounds for each new customer.
Cleaner configuration, fewer surprises
Operators reviewing Tessitura settings for a specific tenant now see configuration that belongs to that tenant, not a global blob of settings that could affect other sites. That clarity becomes important as launch support and ongoing operations mature around connected ticketing systems.