Blog posts
Product Updates
Product Updates

Introducing: Log in with Microsoft and Google

David Simpson
November 29, 2023

Often called 'SSO' or Single Sign-On, you can now use Microsoft and Google accounts that you use every day to log in to Beacon

It's simple, secure, and means that you have one fewer password to remember!

No migration required

Your existing Beacon user accounts can now be logged in to with Microsoft and Google. There's no configuration or migration required.

For example, I usually use the email and a password to log in to Beacon. I use the same email address to log in to Google, so I can now log in to my existing Beacon account using my Google account rather than my password - because the email addresses are the same.

Restrict authentication to your preferred identity provider

Beacon admins have the ability to restrict how your whole charity can log in to Beacon.  Go to Settings > Charity preferences and you will see a dropdown from which you can choose how you want your team to log in.  Once you set this, your team will only be able to log in to Beacon with their Microsoft or Google accounts (whichever you choose). This is useful if you decide that you only want your team to log in via Microsoft from now on.

If you select the default option of Any in the above dropdown, then your team will be able to use their usernames and passwords, Microsoft, or Google to log in.  The same user account, with the same email address, can be logged in to with any of these options.

Users with access to multiple accounts

Some Beacon users have access to multiple accounts. If you log in with your username and password, you won't be able to access any accounts that have restricted identity providers.  If an account is set to only allow authentication with Microsoft then you'll need to log out, and log back in with your Microsoft account.

Business as usual with our other security features

Two factor authentication still works as it did before, you will still need to re-authenticate if your session expires due to inactivity, and Roles and Permissions are unaffected.