Requesting a configuration from your support team
Some Beedeez integration settings are available in the back office and you set them yourself. Others exist, work, and have no screen at all: your support contact configures them for you. This page separates the two, so that you know when to open a request and what to bring to it.
Requesting a configuration from your support team
Some Beedeez integration settings are available in the back office and you set them yourself. Others exist, work, and have no screen at all: your support contact configures them for you. This page separates the two, so that you know when to open a request and what to bring to it.
Settings you can adjust yourself
Check these screens before opening a request.
Sign-in modes. Go to Configuration > Integrations > Authentication. You create and name your sign-in modes there. The modes are Email / Password, SAML, OAuth / OIDC, HR Data and Anonymous, depending on the options active on your account.
The frequency of scheduled jobs. Go to Configuration > Integrations > Jobs & Reporting, open the Scheduled jobs block and click Configure. The jobs listed depend on the options active on your account, among them Synchronization of learning contents in Scorm and SFTP reporting of user activity. This screen sets the recurrence only: the delivery destination and the content of what is sent are configured with support.
The LMS block. Go to Configuration > Integrations > LMS. See LMS-specific connectors for what this block sets.
Provisioning. Go to Configuration > Integrations > Provisioning, blocks Advanced provisioning and SCIM Provisioning. These blocks require the provisioning option to be active on your account.
What the LMS name field tells you
In the LMS block, the Name dropdown offers eight values: WBT, CROSSKNOWLEDGE, CORNERSTONE, TALENTSOFT, SYFADIS, SUCCESSFACTORS, DOKEOS and MOODLE.
Selecting SYFADIS, SUCCESSFACTORS, DOKEOS or MOODLE displays the message For this integration, please contact your support team who will help you to correctly configure the selected LMS. The form stays open, but the setup is not finished on this screen alone: open a request so that support completes it.
ℹ️ Good to know. A name available in this dropdown does not tell you how far the corresponding integration goes on your account. Ask support what the selected platform covers before you plan a rollout around it.
Settings configured outside the screens
Each of the following is set by support and produces a real effect on your account. None of them appears in the back office.
CAS sign-in. Learners reach it through a dedicated address that support gives you, and which you link from your own portal. It adds no button to the standard sign-in page.
Provisioning through calls to your API. When you can neither drop a file nor push SCIM, Beedeez chains calls to your API: get a token, request an extract, wait until it is ready, then fetch it. The result joins the same processing chain as a dropped HRIS file.
The SFTP delivery destination: host, account and key, for the activity export as well as for the SCORM export.
PGP encryption of activity files before they are delivered on your side. In the other direction, an HRIS file you encrypt is decrypted on arrival.
The reporting file format, including a bespoke format whose columns are composed one by one when no ready-made format fits your needs.
Cornerstone, to identify the learner when a piece of content is launched.
CrossKnowledge beyond the fields of its block: publishing your capsules as learning resources in CrossKnowledge, pushing tracking back, and identifying the learner at launch.
Preparing your request
Gathering these four elements before you write turns three rounds of questions into one exchange.
- The need in one sentence, in business terms. Write “new joiners must have an account on their first day” rather than “we need an API”.
- The system on the other side, with its exact version.
- The direction of the exchange: who sends, who receives, and how often.
- Your technical contact, named, and able to create credentials on their side.
💡 Tip: identify the technical contact with your very first request. Access to the HRIS or the LMS rarely belongs to the training team, and obtaining it often takes longer than the configuration itself.
These settings are not displayed back to you in the back office, so keep your own record of what you asked for and of what was confirmed to you. Check the arrival of the first files or the first sign-ins yourself, on the system that receives them.
Going further
- Which brick for which need: choosing between SSO, SCIM and an HRIS file before asking for anything.
- LMS-specific connectors: what the CROSSKNOWLEDGE and WBT blocks set, and what they leave to support.
- Automating activity export to your SFTP: the decisions to make before opening the delivery request.
- Scheduling automatic SCORM package delivery to an SFTP: the job whose recurrence you set on your own.