Identity setup for managed provider teams.

Overview

Single sign-on (SSO) lets your team sign in to BondiByte using your existing Microsoft Entra ID (Azure AD) accounts.

SCIM provisioning foundations help align user provisioning and roles with your identity provider.

These features suit larger or identity-managed provider teams; smaller teams can use standard BondiByte logins.

Before you begin

• Have a Microsoft Entra ID (Azure AD) administrator available on your side.
• Decide which users need workspace access and which only need Staff Portal access.
• Understand that SSO and SCIM complement, not replace, BondiByte roles and permissions.

Recommended setup order

1. Talk to BondiByte about enabling Microsoft SSO for your organisation.
2. Work with BondiByte to provide the identity details your administrator manages on your side, using a safe handover rather than email or chat.
3. Once enabled, your team can sign in with Microsoft on your organisation's login.
4. Where SCIM is used, configure provisioning and group-to-role mapping with admin involvement.
5. Confirm that customer users, Staff Portal users, auditor access, and platform administration remain separate.

Key fields and settings

Best practice

• Use SSO when your organisation already manages identity centrally.
• Keep at least one owner or admin able to sign in during setup.
• Coordinate setup with your Microsoft administrator.

Common mistakes to avoid

• Assuming SSO or SCIM is automatic. Setup is configured for your organisation with admin involvement.
• Assuming SCIM is fully hands-off. Initial setup and role mapping require configuration.
• Assuming SSO replaces roles. BondiByte still enforces its own roles and permissions.
• Sharing sign-in configuration values through unsafe channels such as email or chat.