Connecting Beedeez to your tools

Rights required: access to Configuration, on the parent account.

Two connections tie Beedeez to your information system: authentication and provisioning. They decide who exists on the platform and how people sign in, and both are configured in Configuration → Integration.

The two articles in this section

• Authentication and SSO: who signs in, and how. Your learners enter with the credentials from your identity provider, with no Beedeez-specific password.
• HRIS synchronisation and provisioning: who exists on the platform. Accounts are created, updated and deactivated from your HR system.

The two are often deployed together, but each works without the other: an account created by the HRIS can sign in with a password, and an account created by hand can sign in through SSO.

Not only at launch

Both connections can also be switched on for an account already in production, and that is the more common case. The switch then needs its own preparation: existing users changing how they sign in, accounts to match against the HRIS, duplicates to resolve. Each article has a section on that scenario.

The rest of the integrations

The other connections do not gate learner access. They get plugged in when the need shows up, on an account that is already live:

Need	Where to look
Distribute your content in an existing LMS	Distributing in an LMS
Enrich your capsules with external content	External content
Retrieve your data automatically	Data exports
Drive Beedeez from your own tools	API and webhooks
Plug in Slack, Teams, a calendar	Productivity and communication

These articles are written for your technical teams: they assume access to your information system, your API keys or your LMS. The technical detail of authentication and provisioning also lives on that side: Identity, access and provisioning.

Some configurations cannot be done on your own and go through your support team: LDAP, CAS, SuccessFactors, bespoke formats. See Configurations handled with your support team.