Social Login Key
Overview
Social Login Key — Business Overview
The Social Login Key is used to enable customers, partners, or employees to sign in to Dafater using their existing accounts from popular social platforms such as Google, Facebook, or similar services. Instead of creating and remembering a new username and password, users can access Dafater quickly and securely using a familiar social account.
This document supports smoother user onboarding, better user experience, and reduced login-related support requests.
Purpose in Business Operations
The Social Login Key allows your organization to:
- Simplify access to Dafater for external users and employees
- Reduce barriers during registration and login
- Improve adoption of customer or partner portals
- Strengthen security by relying on trusted external identity providers
It is especially valuable for businesses that interact with a large number of users who are not part of the internal team.
Prerequisites and Setup Requirements
Before using the Social Login Key, the following should be in place:
- A decision on which social platforms (such as Google or Facebook) your business will allow for login
- Approval from management or compliance teams to use social sign-in options
- Clear policies on who is allowed to log in using social accounts (customers, partners, employees, or all)
- Branding and communication guidelines to ensure users understand the login options available
Once these prerequisites are met, the Social Login Key can be created to formally authorize each social platform for use within Dafater.
Typical Workflow and Business Fit
- Business approval is obtained to allow social login for a specific platform
- A Social Login Key is created for that platform
- The login option becomes available on relevant Dafater portals
- Users choose a social account when logging in
- Dafater recognizes the user and grants access based on existing roles and permissions
This workflow fits naturally into customer onboarding, partner engagement, and employee self-service processes.
Key Business Scenarios Where It Is Essential
The Social Login Key is particularly useful in the following situations:
- Customer portals where ease of access directly impacts conversion and engagement
- Partner portals used by resellers, agents, or vendors
- Public-facing applications where fast registration is critical
- Organizations aiming to reduce password reset requests and login support workload
- Businesses expanding to non-technical user groups who prefer simple login methods
Important Considerations for Users
- Social login should align with your organization’s data privacy and compliance policies
- Not all users may be comfortable with social login; traditional login options should remain available
- Each social platform typically requires its own Social Login Key, which must be maintained
- Periodic reviews are recommended to ensure only approved platforms remain active
- Clear user communication helps build trust and avoid confusion during login
Summary
The Social Login Key plays a strategic role in improving accessibility, user satisfaction, and operational efficiency within Dafater. When set up thoughtfully, it supports growth, reduces friction, and enhances the overall digital experience for users interacting with your business.
Basic Information
- Module: Integrations
- Document Type: Document
Fields
| Field Name | Label | Type | Required | Options | Description |
|---|---|---|---|---|---|
| enablesociallogin | Enable Social Login | Check | - | Enable or disable social login access for Dafater users | |
| socialloginprovider | Social Login Provider | Select | Custom, Facebook, Frappe, GitHub, Google, Offic... | Select external provider used for Dafater user authentication | |
| client_id | Client ID | Data | - | OAuth client identifier issued by the selected login provider | |
| provider_name | Provider Name | Data | ✓ | - | Display name of the social login provider in Dafater |
| client_secret | Client Secret | Password | - | Confidential key used to authenticate Dafater with the provider | |
| icon | Icon | Data | - | Icon shown on Dafater login screen for this provider | |
| base_url | Base URL | Data | - | Base URL for provider authentication and API requests | |
| sign_ups | Sign ups | Select | , Allow, Deny | Control whether new users can sign up via this provider | |
| authorize_url | Authorize URL | Data | - | Authorization endpoint URL to initiate social login flow | |
| accesstokenurl | Access Token URL | Data | - | Endpoint URL used to retrieve access tokens from provider | |
| redirect_url | Redirect URL | Data | - | Callback URL where provider redirects users after authentication | |
| api_endpoint | API Endpoint | Data | - | API endpoint used to fetch authenticated user details | |
| custombaseurl | Custom Base URL | Check | - | Enable custom base URL instead of default provider endpoints | |
| apiendpointargs | API Endpoint Args | Code | - | Additional parameters passed when calling provider user information API | |
| authurldata | Auth URL Data | Code | - | Extra authorization URL parameters required by specific providers | |
| useridproperty | User ID Property | Data | - | Field name containing unique user identifier from provider response |
Permissions
| Role | Read | Write | Create | Delete | Submit | Cancel |
|---|---|---|---|---|---|---|
| System Manager | ✓ | ✓ | ✓ | ✓ |