If your organization has signed up for a Suite of Freshworks' Products, which includes Freshservice, your Freshservice account will now be migrated to a common Freshworks account. This means that you will hereafter have a single sign-on (SSO) facility to access the entire bundle of products such as Freshdesk, Freshsales, Freshchat, Freshrelease, etc or any other products your company has opted for and signed up with Freshworks.
With this migration, your agents will have a single profile that is common across all products in Freshworks.
Note: If your organization has signed up with the Freshworks Suite of Products from February 2020, you'll be able to access your Freshservice account using a common Freshworks Organization Account.
What does it change for you?
Changes to Web App Login
Henceforth, agents and requesters will have separate authentication pages. The default login page is meant for requesters, and agents need to click the link meant for agents from the login page and enter their Freshworks login credentials.
↑Login experience for accounts in which the login page has not been customized
↑ Login experience for accounts in which the login page has been customized
If the agent only has a Freshservice account during the migration and not a Freshworks account, they can continue to use their Freshservice account password for the Freshworks account.
- If the agent already has a Freshworks account into which they’ve logged in at least once, they can continue to use their Freshworks login credentials for Freshservice as well.
- If the agent already has a Freshworks account into which they’ve not logged in even once, both their Freshworks and Freshservice password won’t work, and they would be sent an email to set a new password.
- Users that use Google to login to their Freshservice account can continue to use their existing Google credentials. Agents that use Google to login to their Freshservice account will have to first click the link meant for agents from the login page and then choose the Google sign-in option.
Changes to Mobile App Login
- Henceforth, agents who log in to the Freshservice iOS and Android apps need to use the Freshworks login credentials.
Changes to API Authentication
Applications and Integrations that need an email address and password for API access will also use the same Freshworks login credentials.
Changes to Profile Settings Page
Administrators cannot edit certain fields (such as Name, Email Address, Work Phone, Mobile Phone, and Job Title fields) for an agent after their creation. Agents would have to edit these fields for themselves.
- In case an agent wishes to modify these fields (such as Name, Email Address, Work Phone, Mobile Phone, and Job Title) they will need to go the Freshworks profile settings page to do so.
Further details of the agent (such as Time Zone, Language, Location, Reporting Manager, and Signature) can be modified by the agent or the administrator from the Profile Settings page of Freshservice.
Only the default password policy would be available for agents under Freshworks login. Advanced policy settings will be available in a few months.
Changes to Agent ↔ Requester Conversion
When converting an agent to a requester, their Freshservice account will be automatically detached from Freshworks and an email will be sent to reset the password.
When converting a requester to an agent, an invitation email will be sent to them if they already have a Freshworks account.
When converting a requester to an agent, an email will be sent to set a Freshworks password if they don’t have a Freshworks account.
Lastly, agents can now switch between various products seamlessly using the Freshworks Switcher.
Roll out Plan
- We’re currently enabling Freshworks authentication only for accounts that use ID/Password and/or Google authentication.
Freshworks authentication will currently not be enabled for accounts that use Simple SSO, SAML SSO, or Yammer Login.