Put the roster in your team's pocket.

Overview

The BondiByte Staff app gives support workers a phone-shaped view of their work: today's shifts, tasks, reports owing, and expiring documents on one screen, with the rest a tap away.

It is deliberately staff-only. There is no rostering administration, billing, configuration, client or site management, or any organisation-wide view in the app. Those workflows stay in the browser workspace.

It adds what a browser cannot: clock in and clock out with site geofencing, push notifications for shifts and requests, offline access to recently viewed data, and switching between organisations with a tap.

Before you begin

• Confirm the same things the browser Staff Portal needs: an active staff profile, a linked login account, the staff role, and a published roster.
• Decide which sites use clock in and clock out, and whether the geofence should be enforced at those sites.
• Have each site's location saved if you plan to use geofencing, because the check runs against the site's saved location.

Recommended setup order

1. Finish Staff setup and Staff Portal access first. The app enforces exactly the same access rules.
2. Set the organisation-wide clock-in default in Configuration under Rostering rules, then turn it on for the individual sites that need it.
3. Publish the roster in Rostering so shifts appear.
4. Ask staff to search for BondiByte Staff on the App Store or Google Play, install it, and sign in with their existing email and password. Where the account requires it, they complete the same multi-factor challenge as on the web.
5. Ask staff to allow push notifications when prompted, so shift, swap, and request messages arrive.
6. Where a worker is employed by more than one organisation on BondiByte, they can stay signed in to each and switch with a tap.

Key fields and settings

Best practice

• Roll the app out after the roster is published, so the first thing a worker sees is their own shifts.
• Ask staff to allow notifications on first open. Push is the fastest way to reach someone about a shift.
• Turn the geofence on only where it fits the work. Enforcing it can stop a legitimate clock in for community access shifts that start away from the site.
• Point staff at the app for timesheets and shift reports: both are quicker to finish on the phone at the end of a shift.

Common mistakes to avoid

• Expecting the app to do administrator work. It is staff-only by design, and admin workflows stay in the browser workspace.
• Enforcing the geofence organisation-wide without checking which sites have community access work.
• Asking staff to download the app before their login account is linked to an active staff profile. They will reach an access denied screen.
• Assuming an unpublished roster will show. The app sees published shifts only, exactly like the browser portal.