SupportBook a demoTry it free

Monthly access review template set for Jira

Check who has access to what every month, with one subtask per system and an owner for each, created on a schedule in your time zone.

1 work item · 6 subtasks · Monthly

Read: How to run a monthly access review in Jira

Illustration of the Monthly access review template set in the app, with sample data.

The structure

What it creates

Each run creates a Task for that month's review and six subtasks under it, one for each system your team checks. Every subtask is assigned to the reviewer, so each check has an owner from the first day.

Six systems is a starting point. Rename a subtask, add one for a tool you run, or remove one you don't use. Edit the template set, not the work items it created, so next month's run gets the change too.

  • Access review, $todayTask
    • Review Jira accessWho can open each space, and who holds admin rights.Subtask
    • Review email and calendar accessShared mailboxes, delegated access and forwarding rules.Subtask
    • Review code repository accessWho can push, merge and change repository settings.Subtask
    • Review cloud console accessConsole users, their roles, and access keys no one has used lately.Subtask
    • Review HR system accessWho can see pay, personal records and HR reports.Subtask
    • Review shared drive accessShared folders, outside guests and links open to anyone.Subtask

The line under each item is a suggested scope. Write your own in each work item's description.

What fills in

Variables

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.

Variables in the Monthly access review template set
VariableWhat it fills inExample
$todayThe date of the run, in the summaryAccess review, plus the run date
$reviewerAssignee of each subtask; a user variable you addPriya Nair

$today is built in. You add $reviewer to the template set as a user variable, then use it as each subtask’s Assignee. When you apply the set by hand, the app asks who the reviewer is.

When it runs

How to run it

Use one way, or more than one. Each way creates the same structure.

  1. 01

    On a schedule

    Monthly, on the first day, at 09:00 in your time zone.

    The app lists upcoming runs, so you can see the next review before the app creates it.

  2. 02

    On request

    Apply it from the app before an audit.

    The app asks who the reviewer is, so an extra review follows the same steps as the monthly one.

  3. 03

    From Jira Automation

    Call the app's API from a rule.

    Use this when an event in Jira, such as a field change, should start the work.

Who it's for

IT and security leads who run access reviews, and Jira admins preparing for an audit.

It suits teams that already track their work in Jira and want every month’s review to have the same steps, the same owner and the same start date.

When not to use it

If your identity tool already records access reviews, link those records instead of copying them into Jira.

Keep one record of each review in one place. Two copies drift apart, and then someone has to decide which one is right.

Monthly access review: common questions

Can it run on a different day?

Yes. Change the schedule to another monthly time, or write your own CRON schedule, in your time zone.

Who gets the subtasks on a scheduled run?

The person you saved as $reviewer with the schedule.

Does this make us compliant?

No. It gives your team the same review steps every month, with an owner and a record in Jira. Your auditor decides what counts as evidence.

Other template sets that teams use alongside this one.

Browse the template library
Weekly review, $todayEvery Friday
Review open work
Update priorities
Share the notes
ExampleOperations

Review open work with your team at the same time each week.

1 work item, 3 subtasks · Every Friday

See the template set
Onboard $newHire
Create their accounts
Order equipment
Plan the first week
+1 more
ExamplePeople

Accounts, equipment and first-week tasks for each new person.

1 epic, 4 work items · On request

See the template set
Patch rollout, $advisory
List the affected systems
Patch the affected systems
Verify the patch
+1 more
ExampleSecurity

Roll out a vendor patch the same way every time, from listing affected systems to closing the advisory.

1 epic, 4 work items · On request

See the template set
Part of AppsDelivered

Repeatable work, delivered.

Building Jira apps since 2017.

AppsDelivered CommentsReuse your team's replies.See AppsDelivered CommentsAppsDelivered FeedsTurn new posts into work items.See AppsDelivered Feeds