Quickbooky

Accounting News

Time Tracking

QuickBooks Time Kiosk photo capture fails when camera permissions are off

QuickBooks Time Kiosk photo capture can fail over camera permissions or missing webcams; here is how administrators diagnose and fix both.

COMMUNITY ISSUESQUICKBOOKY

QuickBooks Online workplaces that use the Time Kiosk’s photo capture have been running into a familiar wall: the employee taps to clock in, and the camera never fires. The failures are not random. They fall into two camps, permissions and hardware, and the error text on the screen tells you which camp you are in. Photo capture exists to verify that the badge holder is the person at the screen, so a dead camera quietly defeats the point of the feature.

The feature and its two failure modes

Kiosk photo capture is a per-kiosk option inside QuickBooks Time, which most businesses reach through QuickBooks Online. An administrator switches it on for a named kiosk, and every punch after that is supposed to include a snapshot. The reported failures split cleanly in two. Either the device was never granted permission to use its camera, or it has no usable camera at all. The first is a permissions problem. The second is a hardware or browser problem. Telling them apart matters, because the two fixes share almost nothing.

Turning the requirement on

Capture begins as a setting, not a device change. From QuickBooks Online, the path runs through the apps list into Time, then Overview, then Manage kiosks. Standalone QuickBooks Time users find the same screen under Feature Add-ons. Select the kiosk by name, set the photo requirement on clock in and clock out to Yes, and save. Nothing changes on the tablet at that moment. The setting takes hold only after the device is pushed to ask for the camera.

The PIN cycle that surfaces the camera prompt

The step people skip is the one that matters most. On the kiosk device, a manager signs in with the PIN, signs out, and signs in again. That second sign-in is what makes the device ask whether the kiosk may use the camera. Accept the prompt, and follow whatever the operating system requests afterward. On an iPad, that means the Settings app, the Privacy section, the Camera entry, and a switch for the kiosk app. If the prompt is dismissed or never appears, capture stays dormant no matter how the kiosk is configured.

Permission errors and hardware errors read differently

The wording on the kiosk screen does the diagnosis for you. One message tells the employee to have an administrator grant camera access on the device. That phrasing means the setup is correct and the device simply refused the camera. The remedy is the permission grant described above, applied at the operating system level.

A second message tells the employee to have an administrator confirm the device has suitable hardware or software. This one points at the machine itself. Some shared computers ship without a webcam. Others run the kiosk in a browser the feature does not accept. Every deployment needs a camera, whether built in or attached as an accessory.

A third notice, which is not an error, states that camera permission could not be determined. It is aimed at administrators and simply reports that the camera was never set up on that device. It clears once the permission flow finishes.

For hardware cases, the guidance is blunt. On a desktop, run the kiosk in a current release of Chrome, Firefox, or Microsoft Edge. On a tablet, use the QuickBooks Time Kiosk app rather than a browser, and reinstall the app if the camera stays silent after permissions are granted.

Where do the photos go after a punch?

Photos are not left on the device for browsing. They surface on the timesheet. In QuickBooks Online, open Time from the apps list and choose Time Entries; in standalone QuickBooks Time, the same data sits in the Timesheets tab. Any timesheet with kiosk photos carries small thumbnails. Select one to enlarge it, and move left or right when a single punch produced more than one image.

A short checklist before you call it broken

Work through these in order, because most cases close at the second or third line.

  • Confirm the kiosk’s photo requirement is saved as Yes.
  • Run the PIN in, PIN out, PIN in cycle so the permission prompt appears.
  • Grant camera access when prompted, then check the device’s privacy settings.
  • Verify the machine has a working webcam, built in or attached.
  • On a desktop, switch to a current release of a supported browser; on a tablet, reinstall the kiosk app.

Most reported failures end at the permission step, which costs a manager a minute at the device. The hardware cases are rarer and usually involve aging shared machines, where a separate webcam puts the matter to rest.

← Back to Community Issues