From our experience, it's much more efficient to have an onboarding plan defined for each job title, moreover, it's much more comfortable to have it automated as Jira tickets. For example, this workflow could be useful within the onboarding case:
Pre-boarding, where linked issues for workplace preparation are created (newcomer would need a laptop, a list of accesses, documents, etc.)
Day 1, where the real onboarding starts. Here the system could create tickets for office excursion for HR, "meet and greet" for team manager, NDA and policies for the employee
Day 2, and there are more linked issues created: a manager follow-up task to make sure everything is on track, a list of tasks for mandatory trainings
Week 1 status creates a follow-up task for employee's manager and HR to discuss how the newcomer feels about their job and if there is smth to fix.
Onboarded. At this time the employee is considered to be onboarded and the status attribute for the employee is updated to "Onboarded" and the Onboard Employee request is resolved.
Just that easy! In combination with Confluence it could be more efficient and less time-consuming, but having a plan is a good idea in any case.