Some sophisticated deployments of Tines require centrally managing stories in one tenant/team, but deploying them to run in a different tenant/team. For example:

• MSSPs may want to define consistent behavior for their clients' workflows, but have them run in segregated environments for security.

• Enterprises may need runtime data to reside in several independent geographies for compliance reasons.

Story syncing is the solution to these and similar problems. It allows you to build and manage stories in a central location, deploying them as required to different teams or even remote tenants over the network:

See full details in our story syncing documentation. Additionally, syncing can be administered via a set of new Tines API endpoints.