Monthly access review
Check who has access to what, every month, with one subtask per system.
1 work item, 6 subtasks · Monthly
See the template setEach run creates an epic named for the new hire and four work items under it, one per team that takes part. IT, the manager and HR each get their own work item, so everyone knows their part as soon as the offer is signed.
Build a second set for offboarding, the mirror image: remove access, collect equipment and hand over work. It matters even more for security.
$newHireEpicThe line under each item is a suggested scope. Write your own in each work item's description.
Variables fill in what changes from run to run. They work in text fields, such as the summary and description. A user variable fills in a person field, such as Assignee.
| Variable | What it fills in | Example |
|---|---|---|
$newHire | The new person’s name in every summary; a text variable you add | Dana Ortiz |
$manager | Assignee of the manager's work items; a user variable you add | Marco Ruiz |
Both are custom variables. You type the name once when you apply the set, and every work item that uses it fills in.
Use one way, or more than one. Each way creates the same structure.
Apply it from the app when the work starts.
The app asks for any variables, so each run carries its own details.
Add the app's post function to the transition that approves a new hire request.
This works in company-managed spaces. The set is applied the moment the work item moves.
Call the app's API from a rule.
Use this when an event in Jira, such as a field change, should start the work.
People teams, IT and hiring managers at companies that hire often enough for steps to slip.
It suits remote teams, where a missing laptop or login on day one is the first impression.
If your HR system already runs onboarding tasks, connect it to Jira rather than keeping two lists.
Keep personal data, such as addresses and ID details, out of the work items. Use your HR system for that.
As soon as the offer is signed, not on the first day. Equipment and accounts take time.
Yes. Keep a base set for everyone, and a small extra set per role that you apply under the same epic.
Share the template set only with the people who should use it, such as HR and hiring managers. The History page shows who changed it.
Other template sets that teams use alongside this one.
Building Jira apps since 2017.