Roll out Complement in a large organisation

With an enterprise plan, a Complement account manager supports you, and Plan & Billing shows your contract under Enterprise plan. This guide takes your rollout from scoping to monitoring. See View your enterprise contract.

Step 1: scope the project with Complement#

Your account manager sets up the settings that are not made in the app. Agree on them with your account manager before creating accounts:

• the sector, which sets the interface vocabulary. See Vocabulary by sector;
• SSO sign-in with Google or Microsoft. See Enable SSO sign-in with Google or Microsoft;
• white label: a dedicated address, your brand's logos and emails in its name. See White-label your platform;
• the integration with your LMS, described in step 7;
• the other options, such as AI generation or gamification. See Which options should you ask your Complement account manager for?.

Your contract also sets your licences.

Step 2: structure the organisation#

In Admin, choose the Advanced journey: departments, for example a subsidiary, a country or a division, group your teams together. Access to courses is given by team, and tracking can be filtered by department and by team.

Create the structure in Employees with Add a department and Add a team, or let the import create it in step 4. See Organise departments and teams.

Step 3: organise content governance#

Add members from Admin. See Manage the teaching team.

• Set the rights in each course's Settings › Trainer access rights. To keep a course for a few people, remove the others' read rights and turn off Automatically add read rights. See Trainer rights on a course.
• Sort courses by job or by entity with Create folder. These folders are shared by the teaching team. See Manage your courses.

Step 4: create the accounts#

Import your learners in bulk with Import CSV / Excel: one row per person, with their department and team. Missing departments and teams are created. If you do not have enough licences, the review shows how many seats are missing. See Import learners from a CSV or Excel file.

On a platform with SSO:

• for an account created individually, choose SSO account · notification only. See Add a learner;
• in the import file, do not enter a password: each person receives the email inviting them to sign in with your organisation's account.

Step 5: run a pilot, then extend#

1. Publish the onboarding course and turn it on before the first invitations: it only launches at first sign-in. See Launch an onboarding course at first sign-in.
2. Open a first course to one department or a few pilot teams. Read the questions asked to the avatar and the quiz results, then republish your corrections in one go. See Improve a course with analytics.
3. Prepare the communication: the announcement email, backed up by a message from your managers. See Launch a course successfully.
4. Set a Limit completion date and Email reminders. See Inform and remind your learners.
5. Extend: add the other teams in the Access tab. Complement offers to announce the course to the teams you added. See Give access to a course.

Step 6: monitor the rollout#

• Each course's Dashboard gives the figures by team, without learner names. See Read a course's dashboard.
• The Progress tab tracks each learner, with filters by department and by team, and Export downloads this data as CSV. See Export a course's tracking data.
• Usage shows the platform's learning time, course by course. With an hour-credit contract, an alert warns Administrators when the credit is running low. See Track usage.

Step 7: connect your LMS#

The LTI 1.3 integration is set up with Complement: your account manager turns it on, then an Administrator configures it in LMS Config. Your courses are then added as activities in the LMS courses. See Connect your LMS with LTI 1.3 and LMS: add courses, manage groups and grades.

• A teacher or an LMS administrator who opens Complement from the LMS receives a Trainer account, which takes a creator seat, unless they already have an account in your teaching team with the same email address. Plan your seats accordingly.
• Accounts created from the LMS do not go through the first sign-in welcome: the onboarding course does not start by itself for them. To offer it to them, add it to an LMS course and assign it to the LMS default team.
• Complement does not export to SCORM or xAPI.

Step 8: send the requirements to your IT department#

• An up-to-date browser.
• Microphone access allowed in the browser, to talk to the avatar.
• Secure real-time connections (WebSocket) to Complement allowed: spoken exchanges with the avatar go through them.
• The list of domains to allow: ask your account manager for it.

See What are the system requirements for Complement?, Data security and privacy and the Security and compliance (in French) page.

Checklist#

• Sector, SSO, white label and LMS agreed with your account manager.
• Requirements sent to the IT department and tested on a standard workstation.
• Advanced journey chosen, departments and teams in place.
• Roles assigned, enough creator seats, including for LMS teachers.
• Onboarding course turned on before the invitations, pilot completed.
• Access, deadline and reminders set for each course.
• Dashboards, progress and usage reviewed every week.