Screenloop supports Google-based authentication, allowing organisations to streamline login, improve security, and automatically provision user accounts.
Who Can Use This Feature?
Screenloop Admin users
Organisations using Google Workspace
Requirements
Before setting up Google authentication, ensure:
Your organisation uses Google Workspace (not personal Gmail accounts)
You have Admin access in Screenloop
You are able to approve authentication permissions during setup
Enable Google Authentication
To begin setup:
Go to Settings > Authentication
Select Google provider for automatic sign-up
This enables users in your Google Workspace domain to sign in using Google credentials.
Complete the Google Sign-In Flow
During setup:
You will be prompted to sign in with your Google account
Google will request permission to share basic organisational information with Screenloop
Approve the requested permissions to continue
Once completed, Google authentication will be enabled for your organisation.
Manage Authentication Settings
After setup, go to:
Settings > Authentication > Active authentication method > View
From here, you can manage:
Google authentication configuration
Organisation-level sign-in settings
Just-In-Time (JIT) Provisioning
You can enable Just-In-Time Provisioning, which allows:
New users to automatically create a Screenloop account on first login
No manual invite required from Admins
This is useful for scaling onboarding across large teams.
What Happens for Existing Users?
Existing users will automatically be linked to Google authentication
No account recreation or manual setup is required
Users can continue logging in without disruption
Things to Keep in Mind
Only Google Workspace domains are supported (not personal Gmail accounts)
Admin permissions are required to enable authentication
Changes apply organisation-wide once enabled
Ensure users are informed before switching authentication methods
Additional Tips
Enable Just-In-Time provisioning for faster onboarding
Use Google Workspace domain controls to manage access centrally
Combine with role-based permissions for tighter security governance