Employees Arrive From Your HR System, and Their Training Follows

Once our team connects your HR system, the connection gives Elvina a current employee list with the fields training needs: name, work contact, job title or code, location, start date and status. With the connection in place, Elvina proposes a group and a path for each new hire and role change, and a person approves each one before access changes. When a record shows an end date, Elvina proposes removing learning access through the same connection, a person approves the removal, and the completion history stays.

Elvina reads the fields agreed in the pilot and nothing more. It never writes back to your HR system and never acts there on its own.

• Reads: name, work contact, job title or code, location, start date and employment status.
• Left out of scope: pay, bank details, tax forms, benefits, medical notes and performance reviews.
• Never: creates, edits or closes an employee record.
• Never: runs payroll, enrolls anyone in benefits, posts jobs or searches for candidates.
• Always: a person approves each assignment and each removal of access.

Your HR system is connected with our team, nothing is assumed from a product name, and SCIM user provisioning is on the Enterprise plan. Your HR lead, your security contact and our team test the link on a few roles before anyone relies on it.

• Agree on the exact field list with HR and security, in writing.
• Map a few job titles to learning groups, with a reason for each.
• Test a new hire, a role change, a duplicate record and a departing employee.
• Confirm that nothing was written back to the HR system.
• Until then, build groups from a roster you supply.

A fictional golf club hires seasonal staff for the pro shop, the cart barn and the grill each spring, and it promotes a few cart attendants to starter every season. Job titles and start dates live in its HR system, and training has been assigned from memory. Its pilot confirmed the HR connection before anything else.

• Through the confirmed connection, Elvina proposes a seasonal path for each new hire by job title, for the general manager to approve.
• When HR changes a cart attendant's title to starter, the confirmed connection shows it, and Elvina proposes the starter path for the manager to approve.
• The general manager approves both proposals, and the new starter finds the lessons on the Learning Platform.
• When a seasonal hire's end date arrives in the fall, Elvina proposes removing access through the same confirmed connection, and the manager confirms it.
• Nothing in the HR system is changed at any step.

Hiring, pay, benefits and every employment decision stay with your people and your HR system. A person decides how job titles map to training, approves each proposed assignment and handles exceptions, such as contractors who are not in the HR system. Your HR and security teams decide which fields Elvina may read and how long that data is kept.

How do I connect training to my HR system? Agree on a short field list with HR and security, map job titles to learning groups and test the link in a pilot. Once our team has connected it, Elvina proposes training for new hires and role changes, and a person approves each proposal.

• Which HR systems does Elvina work with? Your HR system is connected with our team rather than listed on this website, so ask about your system in the demo. Until it is connected, groups are built from a roster you supply, and assignment and progress work the same way.
• Does Elvina change anything in our HR system? No. Elvina reads the agreed fields and never writes back, creates records or closes them. Payroll, benefits, time off and hiring stay in your HR system and with your people. Learning access in Elvina changes only after a person approves it.
• What about contractors or seasonal staff who are not in the HR system? Add them to a learning group by hand, with a named person approving the change. The HR connection covers only the records it can read. Keep a short list of who sits outside it, and review that list each season.