Slido Settings Integration in Control Hub
After Cisco acquired Slido, IT admins were left managing settings across two separate portals. Every configuration change meant switching contexts, duplicating effort, and hoping the two systems stayed in sync. I designed the integration that brought Slido's organisation-level settings into Control Hub, giving admins one coherent place to manage their entire Webex and Slido deployment.
As Cisco deepened the Slido integration into Webex, IT admins were managing settings across two separate platforms, the Slido admin portal and Control Hub. Every configuration task required switching context, increasing the risk of missed settings and admin frustration at scale.
Organisations using Slido alongside Webex faced a fragmented admin experience. Settings lived in two separate places, org-level and admin configuration in the Slido admin portal, and user management in Control Hub. Admins had to context-switch between platforms to complete basic configuration tasks, with no clear relationship between the two systems.
The goal was to migrate Slido's organisation-level settings into Control Hub, bringing everything under one roof and to do it in a way that felt native rather than bolted on.
The old experience required admins to navigate a standalone Slido portal entirely separate from Control Hub. The redesign brought all Slido configuration into a dedicated tab within Control Hub's Services section, reducing the number of places an admin needs to manage their tools from two to one.
While the hierarchy on both sides appears simple at each level, settings within each tab have been deliberately reorganised to best suit their context, migrating from a fragmented portal into a unified, purposeful structure.
Before designing, I needed to validate whether the proposed structure, a new Slido tab within Control Hub, would actually work for the people managing it. I ran moderated user testing sessions with Figma prototypes, testing the redesigned settings against a set of focused research goals.
Five goals guided each session, designed to test the structure, language, and mental models of the new experience.
Findings largely validated the direction while surfacing two distinct sets of concerns, one around admin access boundaries, one around the transition experience for new-to-Control-Hub users.
Early explorations focused on mapping the Slido settings taxonomy to Control Hub's existing tab and navigation conventions, ensuring the new Slido tab felt native rather than foreign.
Card sorting validated how settings from the old Slido admin portal should be grouped across the four new tabs and identified which settings needed migration from elsewhere in Control Hub.
Findings directly shaped four additions to the original scope, each addressing a specific concern surfaced in testing.
High fidelity screens showing the four-tab structure of the Slido settings integration in Control Hub, General, Features, Privacy, and Present mode.
