Skip to main content
Runbooks

Recurring Work. Automated.

Write the instructions once. June checks your systems, follows the steps, and brings back findings you can act on.

app.juneops.com/runbooks
The right starting point

Run it on your schedule

Recurring checks and everyday requests can each have a process of their own.

On a schedule

Keep recurring checks moving. Choose the day, time, and time zone that fit your team.

Device review · Weekdays at 8:30 AM

From an employee request

Give June a saved process to follow when someone asks for help in a direct message.

“Can I get access to Figma?”

Whenever you need it

Start a run yourself for a one-off review, a spot check, or a process you want to repeat.

App ownership review · Run now
Built around your process

Tell June what good looks like.

You already know how the work should happen. Put that knowledge into a runbook, with clear steps and a useful outcome.

  • Describe the goal in your own words.
  • Choose the tools and the trigger.
  • Test the instructions before making it active.
Find your first runbook
From a run to a result

See the work. Follow the findings.

Review the activity, inspect the evidence, and see a full audit of everything June did.

RunbookDevice compliance review
Completed
Today, 8:30 AM · 1m 42s
Device review complete

Started on schedule · Saved instructions followed

8:31 AM
704devices reviewed
698meet policy
6need attention

Your fleet is in good shape. Six devices need a closer look.

Four devices have overdue security updates. Two have disk encryption disabled. Each finding includes the device, its owner, and the setting to review.

FindingDevicesNext step
Security update overdue4Follow up with device owners
Disk encryption disabled2Review encryption settings

Six employees received a next step in a June DM. No device settings were changed.

Explore the activity, findings, and messages above.

A few good places to start

Use our pre-built runbook library.

Start with one recurring task. Build out the library as your team’s processes grow.

Devices

Device compliance review

Check encryption, security updates, and device health. Give IT a focused list to review.

Every weekday
Software

Renewal watch

Find contracts coming up for renewal, confirm owners, and prepare the next conversation.

Every Monday
Access

Inactive access review

Surface accounts that still have access after an employee leaves, with the evidence in one place.

Every Friday
Requests

Design team access

Give June a repeatable process for checking eligibility and handling software access requests.

Employee request
Devices

Missing device check-ins

Find deployed devices that have gone quiet and identify the people to follow up with.

Every morning
Software

App ownership review

Identify managed apps without a designated owner so every tool has someone accountable.

Run on demand

Frequently asked

What goes into a runbook?

A goal, a set of instructions, a trigger, and the tools June can use. Describe the work in plain language, including what to check, what actions to take, and what the output should contain.

Can I start from an existing template?

Yes. Quick starts give you a starting point for common work across devices, software, contracts, and employees. Tailor the instructions and trigger to match your own process.

Can I test a runbook before making it active?

Yes. Save your work as a draft and use Test to review how the instructions run. When you’re happy with the setup, make the runbook active.

What can I review after a run?

The run record brings together activity, findings, messages, and the execution plan. You can see which steps finished, inspect the details behind a finding, and review the messages June sent.

Give June the work that keeps coming back.

See Runbooks in action