What is the Studio?
The Studio is the latest, revamped version of our CMS (Content Management System).
Why are we revamping our CMS (Studio)?
We decided to rebuild our CMS (Studio) to invest in a best in class user experience for event management across the enterprise. The updates we’re making provide greatly improved performance, a more clear and descriptive user interface, and tee us up for ongoing improvements to performance and scalability.
What is the difference between “CMS” and “Studio”?
In the past, we’ve used these terms interchangeably. We initially started referring to the CMS (Content Management System) as a “Studio” since the launch of our Live Engagement Platform messaging in 2016, though this was limited to marketing positioning. However, from a product and support perspective, we’ve continued to use the term “CMS” to avoid confusing customers.
What are the benefits of moving to the new Studio?
Depending on when customers are migrated, they will immediately see the following benefits:
- Improved performance and for faster navigation (2-5x greater speed)
- More intuitive and descriptive user interface
- Drag-and-drop support for image / file uploads
- Support for larger imports (up to 1k rows)
- Full administration from tablet browsers
- Table support in item descriptions (sessions, speakers, etc.)
- Ability to reset custom individual passwords for attendees
- Easier activity feed monitoring from Event Day within the Studio
- Session locations in maps (coming soon!)
- Other fixes / improvements
For a more detailed explanation of the benefits, see the “Studio vs. CMS: What's Different?” article.
Is there anything that won’t be in the new Studio immediately?
Yes, the following capabilities are temporarily unavailable on the Studio, though we are working quickly to add these to the new environment. Many of these are platform-level add-ons.
If you received notification that your account is being migrated and you are planning to purchase or use any of these capabilities this year, please contact your Account Manager:
- EU server support
- Lead Retrieval + Exhibitor Portal
- Session Scanning
- Content Visibility Permissions
- Meeting Scheduling
- Attendee/Session Recommendations
- SSO/Select/Custom Integrations
- Location-Based Messages
- Sub-Sessions (Nested Agendas)
- Personal Agendas cannot be seen in the UI (can be imported/exported)
- "Only show Personal Agenda" setting
- You have to use email to sign in (no using username/password, unless you integrate with a standard SSO)
- Studio access via handheld mobile devices
- Solid color image options for Topic Channels
We are aiming to have all of these capabilities live in the Studio by Q4 2017, in addition to the enhanced capabilities noted in the “benefits” section above. The only exception to this is Sub-Sessions (nested agendas), which may take slightly longer.
Will prior apps, events and event data remain available from the new Studio?
Yes - all prior apps, events, and event data will remain available from the new Studio. The user experience will be that the app/event picker in the right hand rail of the Studio will list all apps / events (including those created on the old CMS). If a user selects an event created on the old CMS, it will bring the user back into the old CMS environment to view that event and the associated Event Performance analytics, view content setup, etc.
Can prior events created on the old CMS be used to create new events within the Studio?
Yes - all prior events created on the old CMS will be visible within the new Studio (see above), and can be used as templates via the event copying workflow to create an event on the Studio.
Do login credentials change after migration?
No - upon migration to the new Studio, your login credentials remain the same. When logging in, you’ll be launched into the new experience.
What should I expect after my account is migrated? Do I need to do anything?
You do not need to do anything to facilitate the migration to the new Studio. We’ll notify you in advance of your account being migrated and provide you with the timing, and will automatically move your account.
What happens when I create a new event / published app?
When you create a new published app or event, the app or event will be created in the new Studio.
Will my published apps continue to provide access to my past events created in the old CMS?
Unfortunately, no. Once your account is migrated to the new Studio, published apps will only be able to list events created on the new Studio (and will not list events created on the old CMS).
Note that upon migration, there will be no immediate changes to your existing published apps and the events within them. However, the next time you create an event within an existing published app, it will transform that app into a new Studio app, only able to contain events created within the new Studio. (Any other events created in the old CMS that previously existed in that app will no longer be visible)
For example: You have an internal meetings event app with three prior events that were created on the old CMS. You’re then migrated to the new Studio. If you create a new event within that app, it will force the app to be migrated to the new Studio, and the app will only contain the newly created event. It will no longer be able to access the events created on the old CMS.
Of course - the old events can be recreated and added back to the app via event copying workflows, though the typical copying experience will apply (attendees will need to be reloaded, and user generated content / leaderboard rankings will start fresh.)
What specifically happens when I create a new event within a prior published app created on the old CMS?
If you create an event within a published app that was created on the old CMS, a notification will pop up, alerting you that this will migrate that published app to the new Studio, and only the newly created event (and any events created thereafter) will be accessible from within that published app. Any prior events created on the old CMS will no longer be accessible from that app.
If I have any events in the creation (or execution) process during my account migration, will those be tied to the new Studio or old CMS?
Any existing events you have in progress will remain tied to the old CMS. However, if you’d like us to migrate that event and overarching published app to the new Studio, please contact your Account Manager and we’ll do this for you.
Can events created on the old CMS continue to be utilized / managed / updated even after I’ve been migrated to the new Studio?
For now, yes. If you have been migrated to the new Studio, prior events can still be managed in the old CMS, as long as the published app housing those events is still tied to the old CMS (i.e. no new events have been added to the published app, and/or the app hasn’t been republished following the Studio migration). In this case, old events can continue to be managed by clicking on the event in the right-hand rail, which will take the user into the old CMS to manage that event.
Note that in early 2018, the old CMS will no longer be available to manage events, and all events / published apps will need to be tied to the new Studio to be managed. (Event data and copying of old events will remain fully accessible as noted above.)
I would like to start using the Studio. Who can I contact to get access?
We’ll need to make sure your events aren’t utilizing any unsupported features first, as mentioned previously in this FAQ. To get the conversation started, please reach out to your Account Manager.