✅ Your company already uses Control Hub

Check your migration email instructions to confirm if we are taking care of the set up for you or if your own administrator will take care of the set up. Depending on which option, follow the relevant instructions below.

We are taking care of the set up

We will map the Slido subscription to your existing Control Hub organization and set up the licences.

What you need to do:

• Confirm the organization name and your current Control Hub administrator.
• Make sure the Control Hub admin is included in the email and kickoff call. Include the Slido admin in the call if their input is needed.
• Do not use a provisioning link or create another Control Hub organization unless we confirm that you should.

Book the call in your email so we can check the setup and plan the Slido migration with you.

Your own full Control Hub admin is setting it up

The full Control Hub admin named in your email will receive the Cisco provisioning message. The email address used for the order must belong to a full administrator of the existing organization.

What you need to do:

• Use the message to add the Slido subscription to the existing Control Hub organization named in your migration email.
• Do not create a new Control Hub organization.
• If the setup offers to create a new organization, stop. The email has not been matched to the existing organization.
• If it shows “You’re not authorized”, stop. The email was recognised, but the person is not a full administrator.
• Do not provision the wider Slido user group or begin moving users until the migration plan is agreed.
• Book the call in your email and include the Control Hub admin. The Slido admin can join if their input is needed.

What happens after the subscription is provisioned

The exact plan depends on your organization, but the work normally has three stages.

1. Confirm the organization and administrators

We will confirm the correct Control Hub organization, data location, provisioning contact, Slido admin, Control Hub admin and any partner involvement.

2. Prepare and test the setup

Together, we will review the areas relevant to your organization, including:

• Administrator access and roles.
• Member and participant SSO.
• Claimed domains and DNS ownership.
• Data-retention settings.
• Guest collaboration.
• Data location and any cross-region migration.
• A small group of test users.

We will tell you which items are required for your setup. You do not need to complete every item before the first call.

3. Provision users and migrate the Slido organization

Once the setup is ready and tested, we will agree the user list, customer communications and migration date. The Slido team will then coordinate the migration of the agreed users, settings and content and confirm when it is complete.

Who should join the first call?

The right attendees depend on who is completing the setup. Please include:

• The current or intended Control Hub administrator.
• The Cisco partner, if they manage the subscription or Control Hub setup.
• Anyone needed to make decisions about SSO, directory, DNS, security or retention.

The person who currently manages Slido can join if their input is needed for the migration plan, but they do not need to attend every setup call. It is normal for the Slido admin and Control Hub admin to be different people, so their input can also be gathered separately where appropriate.

What should we prepare?

Before the first call, be ready to confirm:

• Whether your company already has one or more Control Hub organizations.
• The name of the correct Control Hub organization, if one exists.
• Whether any company domains are already claimed in Control Hub.
• Who manages your Cisco order and renewal.
• Who should administer Slido in the long term.
• Your SSO, directory and guest-access approach.
• Any data-location or retention requirements.

If you do not know all of this yet, still book the call. We can identify the right owners together.