If has access to an HourBack account, we've sent it a sign-in link. It works once, for 30 minutes.
Nothing after a few minutes? Check your spam folder, or ask an admin at your company to add you under Team. New to HourBack? Set up a pilot
Test link (local and preview only): open
Your email has access to more than one HourBack account. You can switch any time from the menu.
with Hours are per week, from the latest readout. Click a task for its detail.
Your first reports appear here after the pilot's first readout. You'll get an email when they're ready.
Each pilot is one team, with its own pilot code and settings. Reports and trends are per pilot.
Every report so far, newest first. Each person's own report goes only to them.
How the numbers changed from one report to the next. Hours are per week.
Trends start with your first published report and fill in with each one after it.
Who has joined the pilot and whether their HourBack app is running. Apps check in about once an hour, so a status can be up to an hour old.
| Person | Status | Last check-in | Last upload | Computers |
|---|---|---|---|---|
| Loading… | ||||
The install steps appear here once your pilot has started.
Pilot code
· reports
For Windows 10 and 11. A Mac version is planned.
HourBackSetup.exe on the person's computer. It installs for that user only; no admin rights needed.With Intune or another deployment tool, run the installer in the signed-in user's context with:
/AUTOENROLL joins each person with their Windows work sign-in. Their sign-in's email domain must be one of .api.hourback.io (port 443)."%LOCALAPPDATA%\Programs\HourBack\unins000.exe" /VERYSILENTHourBack installs per person, in their own Windows profile. The install script works whether your tool runs it as the signed-in person or as SYSTEM: as SYSTEM, it sets up a sign-in task that installs HourBack for each person who signs in, starting with whoever is signed in now.
powershell -ExecutionPolicy Bypass -File HourBack-Install.ps1To remove HourBack, run the same script with -Remove.
As an app (recommended): wrap HourBackSetup.exe with the Win32 Content Prep Tool and add it as a Windows app (Win32).
"%LOCALAPPDATA%\Programs\HourBack\unins000.exe" /VERYSILENT%LOCALAPPDATA%\Programs\HourBack\HourBack.exe existsAs a script: add the install script as a Windows platform script and set Run this script using the logged on credentials to Yes.
Add the install script to your automation library as a PowerShell script, then run it on the devices (or a policy) for this team. Run it as the current logged-on user if you can; as System works too.
Create a PowerShell script from the install script and run it on the team's computers. Use the logged-on user context where your version offers it; otherwise it runs as SYSTEM and sets up the sign-in task.
Create a PowerShell component, paste in the install script and run it as a quick job on the team's devices. Components run as SYSTEM, which the script handles.
Add the install script as a PowerShell automation and run it as a task on the team's devices. It runs as SYSTEM, which the script handles.
Run the script as a user logon script, or with any tool that runs PowerShell on the computer:
powershell -ExecutionPolicy Bypass -File \\server\share\HourBack-Install.ps1Whatever the tool: the computers need to reach hourback.io and api.hourback.io over HTTPS (port 443), and each person's work sign-in must use one of .
Who can sign in to your company's HourBack account, and what they can see.
A consulting partner can work in your HourBack account at the access you choose. You can change or remove it any time, and everything they do is listed here.
Each client's HourBack account, side by side. What you can open depends on the access each client gave you.
We email your contact to accept HourBack's Terms for their company and choose how much you can see. Nothing is recorded until they do.
Who at can sign in, and which clients consultants work on.
Your clients see your name and logo in HourBack, on their emails and on their reports.
Companies that sign up through it within 90 days are credited to you.
Changes reach people's apps within an hour.
Recording stops, and each person's HourBack app deletes its local activity record at its next check-in. Reports already published stay. To delete the pilot's stored data, contact privacy@hourback.io.
Online billing isn't available yet. During the pilot, invoices come from HourBack directly.
Questions about an invoice: hello@hourback.io