Your helpdesk has two sides: the knowledge base and FAQ, which anyone can read, and the ticket area, where clients sign in to create and track their requests. Chatonio gives you three sign-in methods — magic link, email + password, or SSO from your own app — plus a switch that controls who can create an account at all.
Everything described here lives in Projects → [Your Project] → Knowledge Base → Settings, in the Access & sign-in section. The helpdesk portal itself is not on every plan (compare plans) — see Setting Up Your Helpdesk if you haven't created one yet.
Magic link (the default)
The passwordless default. A client types their email on the login page and receives a one-time sign-in link. Clicking it signs them in — no password to invent, remember, or reset.
- Each link works once and expires after 15 minutes.
- Nothing to configure — it works out of the box.
- Best for clients who visit occasionally: they can never be stuck on a forgotten password.
Email and password
Classic login for clients who visit often and expect a password form. Select Email and password as the authentication method.
- The first login still goes through a magic link: it verifies the client's email, then asks them to set a password.
- After that, they sign in with email + password. The email-link option stays available as the "forgot password" and first-time-login path.
SSO — sign in from your own app
If your clients already have accounts in your product, SSO removes the second login entirely: a user clicks "Support" in your app and lands in the helpdesk already signed in. At a high level:
- Open the Single sign-on section and click Generate secret. Copy it right away — it is shown exactly once.
- Your backend uses that secret to sign a short-lived token (valid for 5 minutes, single use) carrying the user's ID, email, and name. The exact token format and redirect URL are shown under Integration example next to the secret.
- Your app redirects the user to the helpdesk with that token — they arrive already authenticated.
Good to know:
- While SSO is the active method, the public magic-link and password forms are hidden — the login page tells visitors to sign in through your app instead. You can also fill in Send clients here after they sign out to return them to your site.
- Rotate secret invalidates the old secret immediately — update your backend at the same time. The same secret also signs visitors in to your web chat (see Web chat widget: signing visitors in with their account), so rotating it changes both.
- You can't switch the authentication method to SSO until a secret exists, and Turn off single sign-on automatically reverts the helpdesk to magic-link login — so clients are never locked out by a misconfiguration.
- Clients are matched by the user ID in your token. If the ID is new here but an account already uses the same email, the sign-in is refused, with one exception: an account with no user ID yet — a client your team invited, or one created before you turned on SSO — is linked to the user when your token carries
"email_verified": true. Add that claim only when you have confirmed the user owns the address. When a sign-in is refused this way, the client sees "This email is already linked to another account on this help center. Please contact the administrator." - Each sign-in also brings the name in your token: rename a user in your app, and their helpdesk account takes the new name at their next sign-in. The contact's name your team sees changes with it, until someone on your team renames the contact.
Open vs invite-only registration
Independent of the sign-in method, the Who can create an account setting decides who gets one:
- Open (default) — any visitor can create an account from the login page.
- Invite only — self-registration is off. Existing clients keep signing in as usual, but unknown email addresses don't get an account; new accounts come only from your team. This also applies under SSO: a valid token from your app is not enough for a user you haven't provisioned yet, and when a user you have provisioned signs in through SSO for the first time, the token must carry
"email_verified": true(see the SSO section above).
Creating client accounts yourself
Operators can provision helpdesk accounts directly — the only way in for new clients on an invite-only helpdesk, and available in every mode:
- Open the Contacts page and click Add client.
- Choose the Portal client type and enter the client's email (and, optionally, a display name).
- Click Create & send invite — the client receives a welcome email with a sign-in link.
Accounts created this way are treated as verified. On a password-mode helpdesk the invited client is asked to set a password on first login; on a magic-link helpdesk the link signs them straight in.
Telegram chat in the help center
If your project has a Telegram bot, clients can connect their Telegram to their helpdesk account from the helpdesk, and then write to you on Telegram as that account. Your team sees one customer, and tools for signed-in customers work there too.
Switch on Telegram chat in the help center at the bottom of the Access & sign-in section and click Save changes. It is off by default. It can be switched on only while the project has a Telegram bot connected, through a Telegram channel or a Telegram group channel; until then it is greyed out, with the note Connect a Telegram bot first.
Clients then see Chat on Telegram under Submit a Ticket, in the header of each ticket, and on their Settings page in the Telegram chat card. A visitor who is not signed in is taken to the sign-in page first. The button opens one window:
- Open Telegram opens your bot with a one-time link: it works once, only with that bot, for 15 minutes. The client presses Start, and the bot replies that their Telegram is now linked to the account. The window then shows Connected, with Disconnect. If the project has several Telegram bots, each has its own button.
- In a Telegram group appears when the project has a Telegram group channel. Show command gives a
/linkcommand that works once, within 15 minutes. The client posts it in a group your team has already connected to the bot, and the bot confirms in the group. Everyone in that group then counts as this account. Linked groups are listed under Connected groups, each with Disconnect. A group belongs to one account at a time: a command from another account moves it.
A group your team has not connected yet is not linked: the bot replies that the team has to connect it first. The exception is a group channel set to Auto-accept any group, where the command connects the group as well.
A private chat linked here works like one linked from the web chat: the client’s messages to the bot arrive under their account’s contact, and their earlier chats with that bot move in. The details and limits are in Web chat widget: signing visitors in with their account, section Linking a visitor’s Telegram. A linked group keeps its own conversation in your inbox: the account’s contact lists the group under Channels, and the group’s conversation shows the green Verified shield with the account.
A linked Telegram counts as signed in, in the private chat and in a linked group, until it is disconnected. Tools set to Only for signed-in customers then run there for accounts that carry your user ID, that is, accounts your site has signed in through single sign-on or chat sign-in. On a helpdesk where clients only sign in with an email link or a password, linking Telegram still shows your team one customer, with the shield, but these tools do not run. See How to create API integrations, section Tools for signed-in customers.
This is separate from Telegram notifications, which only deliver ticket alerts and do not accept replies: see Ticket notifications for your customers.
Which should you choose?
- Magic link — the safe default for a general audience and occasional visitors. Zero setup, zero password resets.
- Email and password — for clients who come back frequently and prefer a classic login form.
- SSO — when the helpdesk serves your own product's users: one account, no second login, and your app stays in control of who gets in.
- Add invite only in any mode when the helpdesk is for a closed client base — B2B customers, paying accounts, internal teams.
Want the portal on your own domain as well? See Use your own domain for the helpdesk.