Understanding the platform architecture
Storyteq CMP is made up of several connected applications that work together as one system. This page explains how the main parts fit together and how they stay in sync, so you know where each task happens. For an introduction to the platform and its modules, see What is Storyteq CMP?; for how Content Portal relates to the DAM, see Understanding Content Portal and the DAM.
The applications you work in
You work across a few connected applications, each with a distinct role in the system. For what the product’s modules do, see What is Storyteq CMP?.
Content Portal is the front end, where you browse and download assets and use portals. See Understanding Content Portal and the DAM.
Adaptation Studio is where templates are created and adaptations are produced. You reach it from Content Portal through the app switcher.
Platform Administration is the single interface for administering the platform, including users, assets, taxonomy, and configuration.
One sign-in across the platform
The platform uses single sign-on, so you log in once and reach everything you are permissioned for, without signing in to each application separately. Sign-in supports both Storyteq credentials and your organisation’s single sign-on provider.
How the parts stay in sync
The parts are integrated, so an action in one place is reflected in the others automatically.
User management is the clearest example. You create and manage users in Platform Administration, and they are made available across the rest of the platform automatically, so you never add the same user separately in each application. Always manage users from Platform Administration, since the synchronisation flows outward from there.
Templates behave the same way: they are created in Adaptation Studio but surface in Content Portal through integration, for the relevant users on the relevant pages.