Readiness Checklist: Google Single Sign-On (SSO) Before You Begin

Before configuring Google Single Sign-On (SSO) with Badge, please confirm that the following requirements are met. Completing this checklist ahead of time will help ensure a smooth setup and avoid common issues.

 In this checklist, users refers to anyone who logs into Badge, including both Owners and Operators.

 

 

✔ Administrative Access

• You have administrator access to Google Workspace as either:
  • A Super Admin or
  • An administrator with the necessary API Controls privileges
• You have Owner access to Badge

 

✔ Google SSO Scope Confirmation

• Your organization uses Google Workspace accounts for users who will log into Badge
• You are prepared to manage user access to Badge through Google Workspace organizational units
• You have determined which organizational units (or whether all users in your organization) should be permitted to access Badge

Important: Removing a user’s access through Google Workspace will prevent that user from logging into Badge. However, it will not remove the user’s account or record from Badge. Users must still be managed separately within Badge.

 

✔ User Accounts & Email Addresses

• All users who will log in through Google SSO already exist in Badge
• Each user’s email address in Badge exactly matches their email Google Workspace email address
  
  

Important: Badge uses a user’s email address to identify and match them during SSO login. If the email addresses do not match exactly, the user will not be able to log in.

 

✔ Google App Access Readiness

• You know whether your organization restricts access to third-party applications.
  • If third-party applications are restricted, a Google Workspace administrator is available to approve Badge through Google Workspace App Access Control.
  • You are prepared to grant Badge access to the appropriate organizational units.
  • You understand that the Google Sign-In scope must be included when Badge is approved.

Please Note: Some Google Workspace organizations allow Badge to connect automatically. In those environments, users may only need to select Sign in with Google and complete a one-time consent step. Administrative approval is generally required only when your organization restricts third-party application access.

 

✔ Access & Security Planning

• You have reviewed—or plan to review—your organization’s Google session length and session-control policies.
• You have considered whether additional session restrictions are appropriate for users accessing Badge from shared or communal computers.

✔ Communication Planning

• You are prepared to notify users before enabling Google SSO.
• You understand that after Google SSO is enabled, users must log in using Google and can no longer use their Badge email address and password.
• You are prepared to tell users which Google Workspace account they should use when logging into Badge.

Ready to Proceed?

If all items above are checked, you are ready to begin configuring Google SSO with Badge.

Continue to How to Enable Google Single Sign-On (SSO) with Badge