Hand a Learner over to Bud
Bud is a learner management system. From a Learner record, enrola can transfer the learner to Bud. Bud creates them as an applicant and sends them an invitation to register. A Team Owner connects Bud; after that, staff who work on Learners can transfer them.
What enrola sends
enrola sends only:
- the learner's first name and last name;
- their email address;
- their funding model;
- a request that Bud invites them to register.
Bud records the learner, and enrola stores Bud's reference for them. The transfer is one way and happens once. enrola doesn't send later changes, doesn't send documents, addresses or employer details, and doesn't remove learners from Bud.
Connect Bud
Bud gives your organisation its own API details. A Team Owner enters them:
- Open Settings → Integrations.
- In Bud settings, fill in:
- OAuth client ID;
- OAuth client secret;
- Bud API subscription key;
- OST applicant API endpoint and OAuth token endpoint, the two web addresses Bud gives you. Both must start with
https://.
- Click outside each field. enrola saves it.
- In the Integrations section, move Bud from Hidden Integrations to Visible Integrations. It's listed as a Learner Systems integration.
Note. Bud is being made available to organisations one at a time. If Bud isn't in your Hidden Integrations list, ask the enrola team at support@enrola.co.uk to switch it on for you.
Note. OAuth client secret and Bud API subscription key always look empty, even after you save them. Leave them blank to keep what's saved. Type a new value only to replace it.
Transfer a Learner
- Open the Learner record and find Posting control.
- Tick Bud. enrola checks the learner. Anything missing is listed under Bud.
- Fix the learner's details if needed (see below).
- Select Transfer, or Transfer to selected to send to every ticked system.
The log under the panel shows the transfer as Processing, then Success when Bud has created the applicant. Select Show in the Reason column to see Bud's answer, for example "Bud applicant created and invitation requested".
What enrola checks first
| Detail | Where to fill it in |
|---|---|
| A first name | First Name(s), in Personal details |
| A last name | Last Name, in Personal details |
| A valid email address | Email, in Contact details |
| A funding model Bud accepts | Funding Model, in Learning Delivery |
Bud accepts these funding models: Community Learning, 16-19 (excluding Apprenticeships), Adult skills, Skills Bootcamps, ESF, Other Adult, Other 16-19, and Non-funded. It doesn't accept Apprenticeships. For 16-19 learners, enrola also uses Programme Type to tell Bud about traineeships and T Levels. Bud must have the funding model switched on for your organisation.
Only the first name check names its field under Bud. A line such as "This value should not be blank." on its own means one of the other three details is missing.
Messages in the log
| Message | What to do |
|---|---|
| This learner has already been transferred to Bud; another creation is not allowed | Nothing. The learner is already in Bud. |
| Configure the Bud client ID, client secret, subscription key and HTTPS endpoints before transferring | A Team Owner completes Bud settings. |
| Bud transfer requires a first name, last name, valid email and supported OST funding model | Fix the learner's details, then transfer again. |
| Bud authentication did not return an access token | Check the client ID and secret with Bud. |
| Bud rejected the applicant handoff (HTTP …) | Check the learner's details and your Bud settings. Contact Bud if it continues. |
| Bud returned an unexpected success status… / Bud accepted the request but did not return a valid applicant ID… / Bud transfer could not be completed… | Check in Bud whether the learner was created before you transfer again, so you don't create them twice. |