Microsoft Entra SSO
- Sign in with existing Entra ID accounts
- No separate BondiByte password
- Branded login screens
- Controlled emergency access
Security & Access
Role-aware access, hosted in Australia.
Provider teams hold sensitive participant, staff, and operational data. BondiByte is built so the right people see the right things, and access can be granted and removed with confidence.
With Microsoft Entra single sign-on, SCIM provisioning, session control, and access logs, leadership stays in control, and your data keeps Australian data residency.
Enterprise-ready identity, without the friction.
Automated provisioning (SCIM)
- SCIM 2.0 provision on join
- Deprovision on leave
- Group-to-role mapping
- Group-to-site access mapping
Role-aware access
- Owner, admin, manager, and staff roles
- Multi-role users supported
- Staff Portal kept separate from manager tools
- Session revocation
Your data stays yours
- Australian data residency
- Hosted on Microsoft Azure
- Export your operational data
- Access logs for accountability
Control and accountability
Grant access deliberately. Remove it quickly.
Access is role-based, sessions can be revoked when access should end, activity is logged, and emergency access is designed to be traceable rather than a shared back door.
For larger providers, SCIM provisioning and directory sync keep access aligned with your identity provider, so people land in the right role and lose access when your directory says so. Explore SSO & SCIM →
The right people. The right access. Every action logged.
- Sign in
- Verify (SSO or MFA)
- Role and access
- Session control
- Audit trail
Roles, MFA and view-as, in depth.
Access control is one layer with three faces: what a role can do, how a sign-in is verified, and how support staff see what a user sees without becoming them.
Roles & permissions
Coordinators who run rosters without seeing pay, office staff who manage documents without touching billing, support workers limited to their own portal.
- Built-in Owner, Admin, Manager and Staff roles, plus custom roles named for how you work
- Access granted permission by permission, grouped by workspace area
- People wearing two hats hold both roles, and their access combines
- Enforced on the server for every request, not just hidden menu items
- Lockout prevention: at least one active Owner or Admin is always required
Multi-factor authentication
A second check at sign-in from any standard authenticator app, so a stolen password on its own gets an attacker nowhere.
- Works with Microsoft Authenticator, Google Authenticator, 1Password and similar apps
- One-time recovery codes, regenerable whenever you need
- An owner can require MFA for everyone opening the Admin Portal
- Deliberately sequenced: you must verify your own MFA before requiring it for others
- Enrolments, checks and failures recorded, and sessions revocable the moment access should end
View-as (read-only preview)
"It's not showing for me" without borrowed passwords: owners and admins preview the workspace or a staff member's portal exactly as that person sees it.
- Faithful to the person's real role and permissions, page for page
- Strictly read-only, enforced on the server for every action
- A persistent banner and one-click exit, with sessions that expire on their own
- Every preview logged: who viewed whom, when, and why
- Only for users at or below your own level; an Admin can never look through the Owner's eyes
Frequently asked questions.
Can a coordinator run rosters without seeing pay or billing?
Yes. Grant the rostering permissions without the pay and invoicing ones, and that is exactly what they will see.
Are permissions just hidden menu items?
No. Permissions are enforced on the server for every request, so what a role cannot do stays impossible regardless of what appears on screen.
Can we accidentally lock ourselves out?
No. BondiByte requires at least one active Owner or Admin at all times, and Owner and Admin permissions are protected from being edited down. The MFA policy is sequenced so you verify your own MFA before requiring it for others.
Does BondiByte MFA apply to Microsoft SSO sign-ins?
No. SSO sessions are governed by your identity provider's own policies, such as Microsoft Entra conditional access. BondiByte MFA protects password sign-ins.
Can someone change anything while using view-as?
No. While a preview is active every change action is rejected on the server. It is view-only by enforcement, not by convention, and every session is logged.
How should auditors get access?
Through scoped, time-limited auditor invites in the Audit Centre rather than normal login accounts, so their visibility ends when the review does.
Go deeper into security and access.
Each of these has its own page: why it exists, how it works, and the controls that stay with managers.
Feature
Roles & permissions
Configure roles and permissions so each user sees and does exactly what they should.
Explore Roles & permissionsFeatureMulti-factor authentication
Protect sign-ins with a second check from a standard authenticator app, then require it for the accounts that matter most. A stolen password on its…
Explore Multi-factor authenticationFeatureView-as (read-only preview)
Owners and admins can preview the workspace exactly as another user's role and permissions render it, read-only, for users at or below their own role…
Explore View-as (read-only preview)FeatureSupport preview (view as staff)
When a staff member says their portal looks wrong, open a logged, read-only preview of exactly what they see. Diagnose the real problem in minutes…
Explore Support preview (view as staff)Give the right people the right access.
Start your free trial, or book a demo to walk through SSO, SCIM provisioning, role-aware access, and Australian data residency for your provider.