To set up Single Sign-On (SSO) in Papo (https://papo.global/), use social login via OAuth in the admin panel and connect your team's identity provider, such as Google or Microsoft. This lets users sign in to the platform with the corporate credentials they already use, without creating another password. The exact authorization steps and available options appear in the account settings area; check Papo's help center for the current path.
SSO reduces friction in daily access, cuts down on password-related tickets, and helps administrators keep centralized control of the team. Instead of managing yet another set of credentials per agent, the operation relies on the same login used in Google Workspace or Microsoft 365.
| Step | What to do | Goal |
|---|---|---|
| 1. Open the account settings | Access the Papo admin panel | Find the access and security options |
| 2. Choose the OAuth provider | Select Google or Microsoft as the identity provider | Define which corporate login will be accepted |
| 3. Authorize the integration | Review the permissions requested by the provider | Connect the company account securely |
| 4. Test access | Log out and sign in with the corporate account | Confirm that the SSO flow is active |
What Single Sign-On with OAuth is
Single Sign-On is an authentication method in which the user signs in once with an identity provider and then accesses different systems without typing new credentials. In Papo's case, social login via OAuth lets the platform confirm the user's identity with Google or Microsoft, instead of keeping its own password database for that access.
In practice, the agent clicks the option to sign in with Google or Microsoft, logs in to the provider, and authorizes Papo to use the basic identification data. After that, access is granted to the account linked to the corporate email.
How social login works in Papo
The flow follows the OAuth standard, without Papo needing to store the provider's password:
- Login start: the user chooses to sign in with Google or Microsoft.
- Authentication with the provider: Google or Microsoft validates the corporate credentials.
- Authorization: the provider asks whether the user agrees to share the necessary information with Papo.
- Confirmation: Papo receives the confirmation and grants access to the panel according to that user's permissions.
The administrator remains responsible for defining which agents can access the operation, which inboxes each one sees, and which modules are available.
When it makes sense to enable SSO in Papo
Social login via OAuth is especially useful for:
- Teams that already work in Google Workspace or Microsoft 365.
- Operations with many agents and frequent turnover.
- Companies that need more control over who accesses customer service.
- Administrators who want to reduce internal password recovery tickets.
If your team doesn't yet use one of these providers in a standardized way, it may be better to first organize corporate emails and user permissions.
What to prepare before enabling it
Before setting up SSO, check these points:
- Standardized corporate emails: social login links access to the Google or Microsoft email. Personal emails may fall outside the intended flow.
- An available administrator account: keep at least one working administrator access before testing authentication changes.
- Team permissions: define which agents will have access to the panel and which inboxes they will be able to handle.
- Up-to-date documentation: since Papo's interface can change frequently, check the help center or the official website for the exact screen names and provider requirements.
We don't reproduce here clicks or menu paths that aren't documented in the reference materials provided. Papo Global keeps the access and security options in the account settings area.
Frequently asked questions
Is SSO with Google or Microsoft available on any account?
Availability may vary depending on the account type and plan permissions. Confirm in your Papo account's admin area or on the official website whether social login is enabled for your operation.
Do I need a Google Workspace or Microsoft 365 account to use it?
Usually, social login requires an account with these providers. Without a corporate identity in Google or Microsoft, the provider can't authenticate the user to grant SSO.
Does SSO remove the need for a password in Papo?
For the user who signs in with Google or Microsoft, yes: the credential becomes the provider's. Administrator accounts and emergency access should be kept and tested to avoid lockouts.
Can email and password login be kept at the same time?
In many deployments, traditional login and SSO can coexist while the team migrates. Ideally, test both flows before enabling SSO for all users.
What should I do if the social login option doesn't appear?
Check whether the account has administrator permission and whether the integration with the provider was authorized in the panel. To see the current screens and requirements, check the Papo Global help center.
Does SSO apply to customers chatting on WhatsApp?
No. SSO is an internal access feature for panel agents and administrators. Customers continue to be served as usual through the connected channels, such as WhatsApp, Instagram, and email, without needing to sign in to Papo.
Read also
- How to integrate Papo with Microsoft Teams
- How to manage users and permissions within your white label platform
Start for free on Papo Global →
Create your account to centralize channels, CRM, and AI in a single panel.