Tessitura Settings Got a Cleaner Collection Model

Tessitura settings used to rely on global one-off configuration that was hard to manage per site. Tessitura configuration now moves into a collection-based app model, so settings, app state, and public theme data can be handled more consistently across sites.

Scalable across multiple customers

This makes the Tessitura app easier to extend with TNEW, instance data, and customer-specific launch settings. As more organisations adopt Tessitura-powered sites, a collection-based model gives Basker a scalable way to manage configuration for each site without bespoke workarounds for each new customer.

Cleaner configuration, fewer surprises

Operators reviewing Tessitura settings for a specific site now see configuration that belongs to that site, 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.