KDesk Contact Portal Authentication

This article explains the current Contact Sign In and Contact Single Sign-On experience in KDesk, including shared portal links, personalized portal links, sign-in codes, and supported SSO options.

How Contacts Reach the Portal

Teams may share the contact portal in two ways. Some teams send a general portal link that asks the contact to enter their Primary Email. Other teams send a personalized sign-in link that is already tied to the contact record and can move the user directly into the sign-in flow.

If the portal link is incomplete, expired, or no longer valid for that workspace, KDesk shows an error and asks the contact to use a fresh link from the service provider.

Sign In With a Code

KDesk contact sign-in uses a one-time 7-character code. With a shared portal link, the contact first enters the primary email connected to their contact profile. With a personalized portal link, KDesk may send the code as soon as the sign-in page opens.

After the code arrives by email, the contact enters it on the sign-in page to continue into the portal. If a new code is needed, the page also includes a Resend code action. The current experience uses a short wait before another resend is allowed.

Single Sign-On

If the workspace allows contact SSO, the sign-in page can show provider buttons such as Microsoft and Google. Contacts can use those options instead of entering a one-time code.

Some workspaces only allow SSO for contacts whose portal identity matches a synced directory record. When that rule is enabled, KDesk explains that on the sign-in page before the contact continues.

After Sign-In

Once sign-in is complete, KDesk returns the contact to the correct portal workspace and opens the portal area they were trying to access, such as the dashboard, ticket list, or a specific request flow.

Common Issues

• Portal unavailable: the workspace portal is not currently available.
• Invalid portal link: the shared link is no longer valid or is missing required information.
• No sign-in email received: the primary email entered does not match an eligible contact record, or the message may still be on its way.
• Sign-in failed: the code has expired, was entered incorrectly, or the SSO attempt could not be completed.